Single wire bus interface

ABSTRACT

Embodiments disclosed herein address the need for a single wire bus interface. In one aspect, a device communicates with a second device via a single wire bus using a driver for driving the bus with a write frame comprising a start symbol, a write indicator symbol, an address, and data symbols. In another aspect, the device receives one or more data symbols on the single wire bus during a read frame. In yet another aspect, a device communicates with a second device via a single wire bus using a receiver for receiving a frame on the single wire bus comprising a start symbol, a write indicator symbol, an address, and one or more data symbols, and a driver for driving return read data associated with the address when the write indicator identifies a write frame. Various other aspects are also presented. These aspects provide for communication on a single wire bus, which allows for a reduction in pins, pads, or inter-block connections between devices.

CLAIM OF PRIORITY UNDER 35 U.S.C. §120

The present application for patent is a divisional of patent applicationSer. No. 10/851,787, entitled “SINGLE WIRE BUS INTERFACE”, filed May 20,2004, having Attorney Docket No. 030398U1, and assigned to the assigneehereof and hereby expressly incorporated by reference herein.

REFERENCE TO CO-PENDING APPLICATIONS FOR PATENT

The present application for patent is related to the followingco-pending U.S. patent Ser. No. 10/851,526, entitled “SINGLE WIRE ANDTHREE WIRE BUS INTEROPERABILITY”, filed May 20, 2004, having AttorneyDocket No. 030398U2, assigned to the assignee hereof, and expresslyincorporated by reference herein.

BACKGROUND

1. Field

The present invention relates generally to integrated circuits, and morespecifically to communication between master and slave components usinga single wire bus interface.

2. Background

Wireless communication systems are widely deployed to provide varioustypes of communication such as voice and data. Example wireless networksinclude cellular-based data systems. The following are several suchexamples: (1) the “TIA/EIA-95-B Mobile Station-Base StationCompatibility Standard for Dual-Mode Wideband Spread Spectrum CellularSystem” (the IS-95 standard), (2) the standard offered by a consortiumnamed “3rd Generation Partnership Project” (3GPP) and embodied in a setof documents including Document Nos. 3G TS 25.211, 3G TS 25.212, 3G TS25. 213, and 3G TS 25.214 (the W-CDMA standard), (3) the standardoffered by a consortium named “3rd Generation Partnership Project 2”(3GPP2) and embodied in “TR-45.5 Physical Layer Standard for cdma2000Spread Spectrum Systems” (the IS-2000 standard), and (4) the high datarate (HDR) system that conforms to the TIA/EIA/IS-856 standard (theIS-856 standard).

A wireless communication device commonly incorporates multiplecomponents. For example, a baseband processor may interface with one ormore Radio Frequency (RF) or other components. The baseband processormay generate and receive baseband signals, often in digital format. Oneor more Integrated Circuits (ICs) may be deployed to provide functionssuch as analog to digital conversion, digital to analog conversion,filtering, amplification, upconversion, downconversion, and many others.Various parameters and commands may be written to one or more slavedevices by a master device (such as a baseband processor). The masterdevice may need to receive (i.e. read) parameters and other data fromone or more ancillary components (such as RFICs). Such configurations ofmaster devices and slave devices may be deployed in devices outside ofthe communications field as well.

A Serial Bus Interface (SBI) protocol has been deployed in the priorart, which uses three signals to perform communication between a masterdevice and one or more slave devices (i.e. a 3-wire interface). Whilethe SBI protocol allows for multiple slaves to share one interface, somecomponents have demonstrated sensitivity to activity of other componentson a shared interface. Thus, some SBI interfaces have been deployed witha single master and a single slave device, to avoid such interference.Adding additional interfaces, as described, may require the addition ofthree pins (or pads) to the master device for each additional interface.This may add additional complexity and/or cost, due to increased diesize, increased pin count, etc. It is therefore desirable to reduce thenumber of pins required to interface between a master device and a slavedevice.

There exist in the prior art a number of designs for master devices andslave devices that support the SBI interface. It may be desirable toprovide for a new interface to communicate with existing SBI components,to increase interoperability, and to allow for new devices, eithermasters or slaves, to be phased into use with each other, as well aswith legacy components. It is also desirable to provide a means forexisting designs to be modified for communication on a reduced pininterface with a minimum amount of design time to increase time tomarket for new products and speed the rollout of the new interface.

There is therefore a need in the art for a single wire bus interface forcommunication between a master device and one or more slave devices.There is a further need for master devices, slave devices, andconverters that interoperate with existing serial bus interfaces, suchas those adapted to the SBI protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be readily understood by the followingdetailed description in conjunction with the accompanying drawings,wherein like reference numerals designate like structural elements, andin which:

FIG. 1 is a general block diagram of a wireless communication systemcapable of supporting a number of users;

FIG. 2 depicts a portion of a prior art mobile station;

FIG. 3 depicts the formats of the three transfer modes of the SBIinterface;

FIG. 4 illustrates the Fast Transfer Mode (FTM) access type;

FIG. 5 illustrates the Bulk Transfer Mode (BTM) access type;

FIG. 6 illustrates the Interrupt Transfer Mode (ITM) access type;

FIG. 7 depicts a prior art SBI configuration;

FIG. 8 depicts an embodiment comprising a combination of SBI andSingle-wire Serial Bus Interface (SSBI) interfaces;

FIG. 9 illustrates the SSBI transfer format;

FIG. 10 is a timing diagram illustrating an example embodiment of theSSBI signaling scheme;

FIG. 11 is an example master device for supporting SSBI;

FIG. 12 depicts an example master device configured to support SSBI orSBI;

FIG. 13 is an example slave device for supporting SSBI;

FIG. 14 is an example slave device for supporting SSBI and SBI,comprising an SBI slave and an SSBI slave converter;

FIG. 15 depicts the example slave of FIG. 14 configured for SSBI-onlycommunication;

FIG. 16 depicts an example SSBI-only slave comprising an SBI slave andan SSBI slave converter;

FIG. 17 is a timing diagram illustrating SSBI writes, and SSBI mastersignals;

FIG. 18 is a timing diagram illustrating SSBI reads, and SSBI mastersignals;

FIG. 19 illustrates the interrelationship between the clocks in a masterand slave device;

FIGS. 20-22 detail portions of example logic suitable for deployment inan example SSBI master;

FIG. 23 depicts an example embodiment of an SSBI slave;

FIG. 24 is a timing diagram illustrating SSBI writes, and SSBI slavesignals;

FIG. 25 is a timing diagram illustrating SSBI reads, and SSBI slavesignals;

FIG. 26 illustrates example circuitry suitable for deployment in anexample SSBI slave bus interface;

FIG. 27 depicts example logic suitable for deployment as a slaveregisters block;

FIG. 28 illustrates the waveforms showing the end of an example burst,including a termination symbol;

FIGS. 29-31 illustrate example circuitry suitable for deployment in anexample SSBI master, modified to support FTM mode;

FIG. 32 illustrates a portion of an SSBI slave converter;

FIG. 33 depicts waveforms illustrating the start of an FTM transfer;

FIG. 34 depicts waveforms illustrating the end of an FTM transfer; and

FIG. 35 illustrates a portion of additional circuitry for an exampleSSBI slave converter.

DETAILED DESCRIPTION

A detailed description of a preferred embodiment of the invention isprovided below. While the invention is described in conjunction withthat preferred embodiment, it should be understood that the invention isnot limited to any one embodiment. On the contrary, the scope of theinvention is limited only by the appended claims and the inventionencompasses numerous alternatives, modifications and equivalents. Forthe purpose of example, numerous specific details are set forth in thefollowing description in order to provide a thorough understanding ofthe present invention. The present invention may be practiced accordingto the claims without some or all of these specific details. For thepurpose of clarity, technical material that is known in the technicalfields related to the invention has not been described in detail so thatthe present invention is not unnecessarily obscured.

FIG. 1 is a diagram of a wireless communication system 100 that may bedesigned to support one or more CDMA standards and/or designs (e.g., theW-CDMA standard, the IS-95 standard, the cdma2000 standard, the HDRspecification, the 1xEV-DV system). In an alternative embodiment, system100 may additionally support any wireless standard or design other thana CDMA system.

For simplicity, system 100 is shown to include three base stations 104in communication with two mobile stations 106. The base station and itscoverage area are often collectively referred to as a “cell”. In IS-95,cdma2000, or 1xEV-DV systems, for example, a cell may include one ormore sectors. In the W-CDMA specification, each sector of a base stationand the sector's coverage area is referred to as a cell. As used herein,the term base station can be used interchangeably with the terms accesspoint or Node B. The term mobile station can be used interchangeablywith the terms user equipment (UE), subscriber unit, subscriber station,access terminal, remote terminal, or other corresponding terms known inthe art. The term mobile station encompasses fixed wirelessapplications.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any embodiment described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments.

Depending on the CDMA system being implemented, each mobile station 106may communicate with one (or possibly more) base stations 104 on theforward link at any given moment, and may communicate with one or morebase stations on the reverse link depending on whether or not the mobilestation is in soft handoff. The forward link (i.e., downlink) refers totransmission from the base station to the mobile station, and thereverse link (i.e., uplink) refers to transmission from the mobilestation to the base station.

FIG. 2 depicts a portion of a prior art mobile station 106. Theillustrations detailed throughout may also be deployed in other wirelesscommunication devices, such as a base station 104, as well as any otherdevice or devices in which master/slave communication is desired. Inthis example, a baseband processor 220 is deployed in connection withone or more ancillary Integrated Circuits (ICs), as well as othercomponents, not shown. Baseband processor 220 provides communicationprocessing for signals to be transmitted and received, in accordancewith one or more communication systems or standards, examples of whichare detailed above. A typical baseband processor 220 performs digitalprocessing of incoming and outgoing signals, and may perform variousother types of processing, including running various applications. Abaseband processor may comprise various components, including one ormore microprocessors, digital signal processors, memory, and othergeneral or special purpose circuitry of various types. A basebandprocessor may comprise various components for receiving and transmittingsignals according to one or more communications specifications orstandards, such as encoders, interleavers, modulators, decoders,deinterleavers, demodulators, searchers, and various other components,examples of which are well known in the art. A baseband processor mayincorporate digital circuitry, analog circuitry, or a combination ofboth.

The ancillary ICs connected with baseband processor 220 are labeled RFIC230A-230N. Example ancillary ICs include Radio Frequency (RF) ICs, whichmay incorporate various functions such as amplifiers, filters, mixers,oscillators, digital-to-analog (D/A) converters, analog-to-digital (A/D)converters, and the like. The components necessary for communicationaccording to a standard may be incorporated in multiple RFICs 230. AnyRFIC 230 may include components that may be shared for use with multiplecommunication systems. RFICs are shown for illustration only. Any typeof ancillary IC may be connected with baseband processor 220.

In this example, the RFICs 230 receive and/or transmit via antenna 210,through which a link may be established with one or more base stations104. Antenna 210 may incorporate multiple antennas, as is well known inthe art.

SBI Protocol

For communication of various parameters and commands, a 3-wire interfacehas been designed for such communication. This 3-wire interface isreferred to as a Serial Bus Interface (SBI). The 3-wire interfaceincludes a clock line (SBCK), a start/stop line (SBST), and a data line(SBDT). The SBI interface is detailed further below. The SBI interfacedesignates a master device and one or more slave devices. In thisexample, the baseband processor 220 serves as the master, and one ormore RFICs 230 serve as slave devices. The SBI interface is not limitedas such, and the master and slave devices may be of any type. Indetailed example embodiments below, baseband processor 220 may beinterchanged with master device 220, and RFIC 230 may be interchangedwith slave device 230. A baseband processor 220 may also communicatewith various RFICs 230 on various dedicated lines, either analog ordigital, in addition to the SBI bus, not shown.

Note that, as shown in FIG. 2, multiple slave devices may share the samethree master device connections (SBCK, SBST, and SBDT). Various otherconnections between RFICs 230 and baseband processor may be deployed,but are not shown in FIG. 2. A mobile station 106 may also incorporatevarious other components for use in performing communications or runningapplications. Those details are not shown, for clarity of discussion.

The SBI interface defines three types of transfer modes, the formats ofwhich are depicted in FIG. 3. Fast Transfer Mode (FTM) provides formultiple sequences of accesses to any slave, including both reads andwrites. Each access in the sequence identifies the address to which orfrom which the access is to be made.

Bulk Transfer Mode (BTM) provides for multiple sequential accesses to asingle slave. The accesses in a BTM transfer may be reads or writes, butnot both. The address for the bulk transfer need only be transmittedonce. Multiple reads or writes may occur sequentially from this initialaddress.

Interrupt Transfer Mode (ITM) is used to transfer a single byte ofencoded information. The Slave ID (SID) indicates one of two slaves toreceive the message. The 5-bit message field provides for 32 possiblemessages. A pause bit is transmitted after the message.

FIGS. 4-6 depict timing waveforms for FTM, BTM, and ITM, respectively.Each SBI access is performed as follows. Transactions are initiated bypulling SBST low. Transactions are terminated/completed by taking SBSThigh. There is at least one clock in between transactions (SBST and SBDThigh). All changes in the state of SBDT occur prior to a SBCK fallingedge (generally there will be setup and hold parameters specified withrespect to the SBCK falling edge). The first data bit is latched on thesecond falling edge after SBST has gone low. Data is transmitted MostSignificant Bit (MSB) first, Least Significant Bit (LSB) last. (Recallthat for ITM, a single bit identifies one of two slaves, followed by amessage.) Unaddressed slaves wait for the start bit of the nexttransaction. Data may be both read and written during a single FTMtransaction. One or more pause bits are allocated for each bytetransmitted. Both master and slaves release the data bus during pausebits (P) to avoid bus contention.

The first two bits indicate the access type: 01 for FTM, 10 for BTM, and00 for ITM. The Slave ID is 6 bits while the Address and Data fields are8 bits each. Pause bits (P) are inserted after each 8 bits to provideopportunities for the slave to return data without causing buscontention. The first bit of the Address field denotes whether theaccess is a read (1) or write (0). For FTM and BTM, multiple accessescan be done to the same slave without requiring the slave ID to bespecified for each register access. FTM is the usual method ofperforming register accesses. BTM is provided to enable configuration ofa larger group of consecutive addresses. Only the first register addressof the burst is specified. For ITM, the Slave ID field is replaced witha 1 bit SID field to specify which slave to access. Instead of Registerand Data fields, a 5-bit Message field is specified.

In practice, it has turned out that, in some instances, Radio Frequency(RF) ICs 230 are sensitive to interference on a common bus. To avoidthis interference, additional buses have been deployed, to isolate thetraffic on one bus from one or more sensitive devices 230. An exampleconfiguration is shown in FIG. 7. In FIG. 7, baseband processor 220communicates with RFICs 230A-230J on individual 3-wire SBI busesdedicated to each device. In this example, additional RFICs 230K and230N are connected with a shared SBI bus. Although adding buses canresolve interference, it increases the number of pins required for thebaseband processor 220, as well as the number of master controllers. Forexample, a baseband processor 220 may be deployed with 3 or 4 SBI ports,requiring 9 or 12 pins, respectively. The design may be complicated byoverhead required to share the available ports between the variousexternal chips 230.

SSBI Protocol

To provide the reduced interference desired for sensitive ancillarychips 230, while reducing pin count, a new single-wire bus interface isprovided, detailed further below, referred to as a Single-Wire SerialBus Interface (SSBI). FIG. 8 depicts an example mobile station 106deployed with an independent single-wire (SSBI) bus connecting each RFIC230A-230J with baseband processor 220. 3-wire SBI buses may also bedeployed in combination with SSBI buses, if desired. This is illustratedas shown with a shared 3-wire bus connecting RFIC 230N-230K and basebandprocessor 220. Deploying the single-wire interface allows for reducingpin count, increasing the number of ports, or both. Increasing thenumber of ports may alleviate the design complication, mentioned above,that may occur when two or more devices need to share a bus interface.Note that, for clarity, in example embodiments detailed below, the SSBIinterface may be explained with respect to pins and/or pads. The SSBIprotocol is also applicable to inter-die connections (i.e. pad to padconnections, without pins), as well as inter-chip connections (i.e.block to block connections, with neither pads nor pins). Those of skillin the art will readily adapt the principles disclosed herein to applyto these and various other embodiments.

Alternate embodiments may include any number of single-wire buses, aswell as any number of 3-wire buses. In various embodiments, examples ofwhich are detailed below, pins may be configurable for use with either a1-wire or 3-wire bus interface.

The example SSBI protocol detailed herein has the following properties.The pin count required is reduced with respect to the SBI interface. Thebandwidth may be comparable to or better than the SBI interface. Theaddress is increased to support additional registers, thus supportingincreasingly complex slave devices. In this example, the number ofaddressable registers is 256.

To reduce the number of pins, the SSBI does not include the clock line(SBCK) and the start/stop line (SBST). The single line in the SSBIprotocol is referred to herein as SSBI_DATA. The clock line having beenremoved in the interface, a local clock is used at both the master andthe slave device instead. The local clocks at the master device and anyslave devices do not need to be identical. The protocol accounts foroffsets in phase and frequency, as detailed further below. A certainamount of frequency error is tolerated, the amount depending on thespecific embodiment. The SSBI protocol is phase independent with respectto the clocks of the master and slave devices. The local clocks may begenerated using local oscillators, derived from other clock sources, orvarious other clock generation techniques known in the art. The SSBIinterface

Instead of a start/stop line, a start bit is inserted into the datastream, and an idle state (IDLE) is defined. A receiving device (i.e. aslave) may monitor the data line (SSBI_DATA), sampling the predeterminedIDLE values, and then beginning a transaction when a start symbol isdetected. When a transaction is completed, the data line may be returnedto the IDLE state, thus terminating the transfer.

The SSBI protocol may be designed with timing and waveforms selected soas to facilitate an interface between 1- and 3-wire interfaces. As willbecome clear, this allows for migration from the 3-wire SBI protocol tothe 1-wire SSBI protocol. For example, a master device may be equippedwith a logic circuit for generating both SBI and SSBI formats, tofacilitate communication with earlier generation slave devices, as wellas newer slave devices as they are produced. In similar fashion, anexisting slave device may be equipped with conversion logic such thateither SBI or SSBI formats may be received, allowing interoperabilitywith both earlier generation master devices and new master devices. Aslave may be equipped with 3 pins for the 3-wire mode, a single pin ofwhich is dedicated for SSBI_DATA when in SSBI mode. The mode may beselected by setting pre-defined values on the unused pins when SSBI modeis desired. Furthermore, a single pin slave device may be quicklydeveloped by adding conversion logic to the existing core, such that asingle wire SSBI_DATA may be translated into legacy 3-wire SBI signals,for interfacing with the existing core. Such conversion logic, detailedfurther below, may be added to a slave device with minimal impact on theexisting functionality, allowing the new device to be developed rapidlywith high confidence. The benefits of reduced interference due toseparate control lines, and pin count reduction at the master and/orslave devices may thus be achieved during a migration in the marketplaceto three-wire devices to single-wire devices. Various exampleembodiments are detailed below.

Table 1 shows the SSBI interface signals. The SSBI interface consists ofa single pin per device called SSBI_DATA. SBST is removed since thestart and end of a transfer are denoted in the data stream itself. SBCKis removed, as there is a common clock at both the master and slave. Itis presumed that there is a clock available at both the master andslave, referred to at SSBI_CLK. Any common clock may be used. There isno phase relationship required between the master and slave clocks. Inone embodiment, to simplify routing, the two clocks may be derived fromthe same source. The two clocks should generally be the same frequency,although some frequency error may be corrected for. Those of skill inthe art will readily tailor the amount of frequency error allowed forany given embodiment in light of the teaching herein. This clock needsto be on whenever SSBI communication is required.

TABLE 1 Modified SSBI Master Port Descriptions Signal DescriptionSSBI_DATA SSBI Data line; bidirectional; connects master device (i.e.baseband processor 220) to slave device (i.e. RFIC 230) SSBI_CLK Localclock; generated at each master and slave device for 1-wire operation

In an example embodiment, the master device 220 comprises a pad forSSBI_DATA with the following characteristics: The pad is bidirectional.It supports drive strengths of 2 mA in low-drive mode and 5 mA inhigh-drive mode (this is consistent with the settings used for exampleSBI pads). The example pad contains a selectable pull-down device, and aselectable keeper device. Various other pads may be deployed within thescope of the present invention. In alternate embodiments, such asinter-block connections on a single die, for example, pads may besubstituted with alternate components, such as tri-state drivers, muxes,and the like, as is well known by those of skill in the art.

In the example SSBI protocol, only one mode is supported, and only oneregister access per transfer is supported. It may be thought of as asimplification of FTM, without the need to specify the mode or slave ID.Since there is only one slave expected on the bus (although addressingschemes may be used if two or more devices are desired, describedbelow), the slave ID bits are no longer required. As a result, there isvery little overhead for each access when compared to the SBI commands.The multiple 3-wire SBI modes provided mechanisms for removing unneededoverhead in order to improve bandwidth and reduce latency. The singleSSBI format provides the same benefits.

FIG. 9 illustrates the SSBI transfer format. A frame may be a read frame920 or a write frame 910. The first bit denotes whether a read or writeis performed. Read access is indicated by ‘1’ and a write access by ‘0’.This assignment is not arbitrary, but in fact it prevents the Slave fromaccidentally seeing the read operations if the SSBI master block isinadvertently reset in the middle of an access. The Address field is afull 8 bits, and since the read/write indication is separate, all 256addresses are now available to both reads and write registers. In theexample embodiment, the address space is increased in SSBI vs. SBI. Inalternate embodiments, any address space size may be deployed.

The Data field is parameterized in various embodiments described below,and can be in range from 1-16, for example. This parameter is identifiedbelow as SSBI_DATA_WD. For both address and data fields, the values areoutput MSB first. For writes, since the master continuously drives thebus, no Pause bits (P) are required. For reads, pause bits are used. Toperform additional reads or writes, a new command is initiated on thebus. This way, the slave always knows to expect 17 symbols for a write,and 19 symbols for a read (when SSBI_DATA_WD=8).

While it is expected that one slave will be supported per SSBI port, itis possible to support two slaves by having each respond to a differentset of SSBI register addresses. For example, one slave could respond toaddresses 0-127, while the second responds to 128-255. By using such anapproach, however, there may be loading issues on the board plus theusual interference problems, as described above for the SBI protocol.

FIG. 10 is a timing diagram illustrating an example embodiment of theSSBI signaling scheme. In this example, the data line (SSBI_DATA) is lowwhen indicating the idle state. When data is to be sent, a start bit istransmitted, a high voltage (or “1”), in this example. The start bit isused to center the receiver's sample point for sampling the incomingdata stream. Following the start bit is a stream of data. Since thecommand formats are well defined, the receiver can determine from thedata stream precisely how many bits will be sent. Thus, the receiverknows when the transfer will complete, and can reenter the idle state towait for the next start bit. The start bit and data bits are each twoclock cycles long, in this example, hence the symbol period is twocycles long. The data bits are transmitted high or low depending onwhether a 1 or 0 is being sent. In an alternate embodiment, each bitcould be one clock cycle long. However, in such a case it may bedifficult for the receiver to find the center of a symbol since therewould be only half a clock cycle of accuracy. Thus, the receiver couldnot guarantee it would avoid sampling the symbols when they aretransitioning. With the symbols being two clock cycles long (or longer),the receiver can guarantee it is sampling the symbols somewhere between0.5 and 1.5 cycles into the symbol, hence at least 0.5 clock cycles awayfrom any transitions. The number of clock cycles per symbol may vary inalternate embodiments.

The clock at the receiver need not be aligned with the data. So, inessence, the SLAVE CLOCK depicted in FIG. 10 may shift left or rightwith respect to SSBI_DATA. In this example, the receiver starts samplingat the first falling clock edge after SSBI_DATA goes high. The samplingpoints are denoted by the dotted vertical lines. Each subsequent symbolis sampled every two clock periods from that point until the access iscompleted. Following the IDLE bit, another start symbol may betransmitted.

This SSBI protocol is resistant to frequency error. The allowed amountof such error may be varied based on the design choice in deployment ofany particular embodiment. If an external clock is deployed and routedto one or more of connected components, the interface successfullyoperates in the presence of variable clock skew between the variouscomponents. Alternatively, one or more connected components (i.e. themaster and/or any slaves) may generate their own clock, within thefrequency error requirements as designed.

The transfer time of any access is not data-dependent. Transfer timesare the same as for the example 3-wire SBI bus interface. Any voltagelevels may be chosen for the various bit types, as will be clear tothose of skill in the art. In this example, as described above, thestart symbol is selected to be “1” (or a high voltage) to center thesample strobe. Idle is set to “0” (or ground). This simplifies theinterface with unpowered chips. For example, RF chips (or other slavedevices) may be powered on and off to conserve power. Setting idle toground simplifies this condition.

In general, the master drives SSBI_DATA. The only time the mastertri-states the bus is while read data is being driven by the slave. Atall other times, the master drives the bus. Since both the master andslave devices will at different times drive the data bus, to avoidcontention on the data line, the present driver of the bus releases thebus for one symbol period (two cycles in this example) prior to the nextdevice being allowed to drive the bus. This duration will be referred toas a Pause bit. Pause bits are identified by “P” in FIG. 9. For thePause bit, the value on the data line may be held using a pad keeper, ifone is deployed. It is expected the slave will respond with read data,using the same timing as the receiver approximates the master is using,hence the read symbols should appear approximately where the masterexpects them.

To understand the transition between drivers, consider the following:Subsequent to the master sending the LSB of the Address field for a readaccess, a Pause bit is transmitted to allow time for the master torelease the bus. The slave responds by driving D7 through DO, followedby releasing the data line for another Pause bit. The master may thenrecapture control of the bus to transmit the next symbol. Contention isavoided since the slave knows the master's timing to an accuracy of halfa clock cycle based on the start bit. Since the Pause bit is two clockcycles, it may appear as short as 1.5 cycles or as long as 2.5 cycles,depending on the relative phases of the master and slave clocks. As longas the bus delay is less than 1.5 cycles, there will be no contention.

The 3-wire SBI interface has a SBST signal that asserts for the durationof the transfer and deasserts when the master is done. This makes iteasy to forcibly put the slave into the idle state at any time. Themaster may ensure SBST is deasserted and, whether the slave is alreadyidle or in the middle of a transfer, it should realize there is nolonger a transfer and enter the idle state. With the 1-wire SBIinterface, there are no signals to clearly specify this. Consider twocases: first is during power on reset, and second during normaloperation. During power on, a master may take into, consideration theamount of time required to reset the various devices, and ignore SSBIactivity until the reset is complete. During normal operation, as longas the master and slaves remain in sync, such that the slaves respondonly to the master and that the master SSBI block is never forciblyreset during a SSBI transfer, there will be no issue.

If there is a need to reset the SSBI master at some arbitrary time, forwhatever reason, it is possible that the SSBI bus may be in the middleof a read, hence a slave device will be driving the SSBI data bus. Ifthe master is forced into Idle state, it will also drive the data bus;hence there may be contention. When the slave is not driving the bus, inresponse to a read access, the master entering idle will not causecontention. The slave will either remain in the idle state, or completeany current write access, then enter idle state. (In this example, sincethe 1-wire formats are such that writes and reads are 17 and 19 symbolperiods long, for data width of 8 bits, at most, 19 symbol periodslater, the slave is guaranteed to be in Idle state). To solve the issuewhen the slave may be driving the bus, the master may refrain fromactively driving the SSBI_DATA line until it is determined that thepossible contention period is over. In the example embodiment, themaster will tristate SSBI_DATA and enable a pull-down device in the pad.A command to reset a control register may be used to indicate that thepull-down may be disabled. In an alternate embodiment, a write accesscommand may be used to re-enable active control of the bus by themaster, disabling the pull-down, if desired.

Converting Between SBI and SSBI

Described above are two protocols, SBI and SSBI, which may be supportedusing 3-wire or 1-wire interfaces (perhaps requiring some conversionfeatures). Many devices in operation today support the SBI protocol on a3-wire interface. Example embodiments, various examples of which aredescribed herein, may include a master device 220 and one or more slavedevices 230 that communicate using SSBI on a single wire interface. Anexample master device 220 for supporting SSBI is depicted in FIG. 11,and a corresponding slave device 230 is depicted in FIG. 13. It may bedesirable for a master device 220 to support both SBI and SSBI on eithera 1-wire or a 3-wire interface, or a combination of both. An example ofsuch a master is depicted in FIG. 12. Similarly, a slave device may beconfigured to receive either protocol on either a 1-wire or a 3-wireinterface. An example of such a slave device is depicted in FIG. 14.

FIG. 11 depicts an example master device 220 configured for SSBIcommunication on a single wire. A microprocessor, or other device,communicates with the SSBI master 1110 to perform read and writeaccesses (details not shown). SSBI master 1110 may also receive orgenerate other commands or signals, examples of which are detailedfurther below. The master device 220 transmits and receives data onSSBI_DATA, which is connected to pad 1120. An example pad is describedabove. The pad input (PI) is delivered to SSBI_DATA_IN on SSBI master1110. The output for pad 1120 is received from SSBI_DATA_OUT of SSBImaster 1110. The pad is enabled (or driven) in response to SSBI_DATA_OEfrom SSBI master 1110. Other functions such as keepers and pull devicesmay be deployed as well (details not shown). SSBI master 1110 transmitsand receives according to the SSBI protocol.

FIG. 13 depicts a slave device 230 configured for SSBI communication ona single wire. Various blocks, registers, functions, etc., may interfacewith the SSBI slave 1310 (details not shown). SSBI slave 1310 mayprovide data from write accesses, and source data for read accesses, asdirected by a master device, such as device 220 shown in FIG. 11. SSBIslave 1310 may also receive or generate other commands or signals,examples of which are detailed further below. The slave device 230transmits and receives data on SSBI_DATA, which is connected to pad1320. An example pad is described above. The pad input (PI) is deliveredto SSBI_DATA_IN on SSBI slave 1310. The output for pad 1320 is receivedfrom SSBI_DATA_OUT of SSBI slave 1310. The pad is enabled (or driven) inresponse to SSBI_DATA_OE from SSBI slave 1310. Other functions such askeepers and pull devices may be deployed as well (details not shown).SSBI slave 1310 transmits and receives according to the SSBI protocol.

On a baseband processor, such as a master device 220, a bank of pins maybe configurable to provide a combination of single and 3-wireinterfaces. For example, 12 pins may be allocated, and configurable toprovide a variety of bus combinations. For example, 12 single-wireinterfaces or four 3-wire interfaces may be deployed. Or, one 3-wireinterface may be deployed with 9 single-wire interfaces. Or two 3-wireinterfaces may be deployed with 6 single-wire interfaces. Or, three3-wire interfaces may be deployed with 3 single-wire interfaces. Alimited subset of the pins may be deployed to be configurable inmultiple bus interface types as well. Pins may be alternatelyconfigurable for non-SSBI or non-SBI purposes as well. Those of skill inthe art will recognize that myriad combinations of pins and configurablebus types may be deployed within the scope of the present invention.

By switching to single-wire buses, additional buses may be deployed withfewer pins, and the number of components sharing a bus may be reduced.For example, deploying point-to-point single-wire buses allows forreduced interference when compared to a shared bus, and the schedulingof traffic becomes simpler and latency issues may be avoided, aspoint-to-point connections remove the bandwidth scheduling required on ashared bus.

FIG. 12 depicts an example master device 220 configured to support SSBIor SBI. Three pins are shown, which may be used for a 3-wire interface,or alternately for three 1-wire interfaces. There are three SSBI masters1110A-C, and an SBI master 1220. Three pads 1250A-C receive signals viamuxes 1230A-C and 1240A-C, respectively. The muxes are controlled via asignal SSBI_MODE, which indicates whether SBI or SSBI mode will beselected. 82 An SBI master 1220 is known in the art, and is not detailedherein. An example embodiment of the SBI master 1220 may be of any type.Those of skill in the art will readily adapt prior developed SBI devicesor circuits, or may devise new ones, to perform the requirements of anSBI system, as described above. Example SSBI masters 1110 are detailedfurther below. An example SSBI master may perform the SSBI protocol, asdescribed above, and may also perform according to the SBI protocol, inorder to facilitate compatibility with other devices (described furtherbelow).

Pad 1250A is used to provide SBCK in SBI mode, and is SSBI_DATA0 in SSBImode. The pad input (PI) is delivered as SSBI_DATA_IN to SSBI master1110A. The pad output comes through mux 1230A, and is SSBI_DATA_OUT fromSSBI master 1110A in SSBI mode, and SBCK from SBI master 1220 in SBImode. The output enable (OE) comes through mux 1240A, and isSSBI_DATA_OE from SSBI master 1110A in SSBI mode, and set to high duringSBI mode (because SBCK is not a tristate signal, it is always anoutput).

Pad 1250B is used to provide SBST in SBI mode, and is SSBI_DATA1 in SSBImode. The pad input (PI) is delivered as SSBI_DATA_IN to SSBI master1110B. The pad output comes through mux 1230B, and is SSBI_DATA_OUT fromSSBI master 1110B in SSBI mode, and SBST from SBI master 1220 in SBImode. The output enable (OE) comes through mux 1240B, and isSSBI_DATA_OE from SSBI master 1110B in SSBI mode, and set to high duringSBI mode (because SBST is not a tristate signal, it is always anoutput).

Pad 1250C is used to provide SBDT in SBI mode, and is SSBI_DATA2 in SSBImode. The pad input (PI) is delivered as SSBI_DATA_IN to SSBI master1110C, as well as SBDT_IN to SBI master 1220. The pad output comesthrough mux 1230C, and is SSBI_DATA_OUT from SSBI master 1110C in SSBImode, and SBDT_OUT from SBI master 1220 in SBI mode. The output enable(OE) comes through mux 1240C, and is SSBI_DATA_OE from SSBI master 1110Cin SSBI mode, and is SBDT_OE from SBI master 1220 during SBI mode.

The interface to a microprocessor, or other device issuing accessrequests, is not shown. Each SSBI master 1110 and SBI master may beequipped with an interface for performing read and write accessesthrough the respective SSBI or SBI interface. In alternate embodiments,multiple devices may share an interface with an SBI or SSBI master, andthus an arbiter may be deployed to arbitrate accesses between themultiple devices (not shown).

In an alternate embodiment, an SSBI master may be deployed to supportboth SBI and SSBI protocols, with 1-wire or 3-wire support, as desired.While such an embodiment is not detailed, those of skill in the art willreadily adapt the embodiments described herein to perform this support,if desired.

The master device 220 depicted in FIG. 12 is one example of a devicesuitable to migrate from 3-wire techniques to single wire techniques.Master device 220 is capable of communicating with legacy 3-wire slavedevices, using the SBI protocol. It is also capable of performing SSBIcommunications with up to 3 different single-wire slave devices, such asslave device 230 shown in FIG. 13. If desired, an SSBI master 1110 maybe modified to support all or part of the SBI protocol, as desired, forcompatibility with other devices.

One technique for migrating from a 3-wire SBI interface to a single wireinterface for a slave device 230 is depicted in FIG. 14. In thisembodiment, an SBI slave 1410 (which may be a new design, or may be anySBI compatible device already designed) is coupled with SSBI slaveconverter 1420. Accesses are performed (writes to or reads from) theslave device 230 via an interface with SBI slave 1410 (not shown). SBIslave device 230 communicates using 3 wires, and the SBI protocol. The 3wires are intercepted by the SSBI slave converter 1420, which performsconversion required to allow single-wire communication. In this example,3-wire communication is also supported, so that this slave 230 maycommunicate with either an SBI or SSBI master. Example SSBI slaveconverter embodiments are detailed below, and others will be apparent tothose of skill in the art in light of the teachings herein. In alternateembodiments of slave devices 230, an SSBI slave may be designed tosupport both protocols. One advantage of designing a converter 1420, asshown in FIG. 14, is that an existing slave device 230 may already bedesigned with a 3-wire interface, and to speed time to market with a newsingle-wire interface, a converter may be simply inserted into thedevice without the need to redesign the existing core.

In the slave device 230 of FIG. 14, the SBCK input is received via pad1430 and delivered to SBCK_IN of SSBI slave converter 1420. The SBSTinput is received via pad 1440 and delivered to SBST_IN of SSBI slaveconverter 1420. These inputs are used for SBI communication, and may beused to enable SSBI mode otherwise (as detailed further below). Pad 1450receives and transmits SBDT in SBI mode or SSBI_DATA in SSBI mode. Thepad input (PI) connection to pad 1450 is connected to both SSBI_DATA onSSBI slave converter 1420 and SBDT_IN of SBI slave 1410. The pad output(PO) and output enable (OE) connections to pad 1450 come fromSBDT_PO_OUT and SBDT_OE_OUT of SSBI slave converter 1420, respectively.SSBI slave converter 1420 also receives a clock input, CLK, at SSBI_CLK,and a reset signal RESET. These signals may be generated internally toslave device 230, or may be generated externally.

SSBI slave converter 1420 generates and receives SBI signals forinterfacing with SBI slave 1410. SBCK_OUT and SBST_OUT are generated andconnected to SBCK and SBST of SBI slave 1410, respectively. SBDT_PO andSBDT_OE are intercepted and received at SSBI slave converter 1420 asSBST_PO_IN and SBDT_OE_IN, respectively.

This example embodiment SSBI slave converter 1420 also generates othermiscellaneous signals. SSBI_MODE indicates, when asserted, that theslave device 230 is operating in SSBI mode. Otherwise, the slave deviceis operating in SBI mode. This signal is used for conversion, detailedfurther below, and is delivered as an output for optional use byexternal blocks. Signals for managing clock disabling are alsogenerated, which may be used to disable and enable one or more clocks,for power savings, or other purposes. The signal TCXO_DIS is asserted todisable a clock. The signal RESET_TCXO_DIS is asserted to reenable theclock. Example embodiments illustrating the use of each of the signalsdepicted in FIG. 14 are detailed further below.

An SSBI Slave Converter block 1420 may determine whether the slave is in1-wire or 3-wire mode, in order to mux between these modes. Modedetermination may be performed by examining SBCK and SBST from the pads(i.e. pads 1430 and 1440). In 3-wire mode, there is never a conditionwhere SBST=1 and SBCK=0, hence that condition may be used to assertSSBI_MODE which controls SBI/SSBI muxing. As mentioned above, in thisexample, SSBI_MODE is also output from the SSBI slave converter 1420 incase it is needed for various other purposes. Example embodimentsillustrating this functionality are detailed below.

A slave device 230, as shown in FIG. 14, may be used for either 1-wireor 3-wire communication, as described above. In an example embodiment,this slave device 230 may be configured to support only single wire SSBIcommunication. FIG. 13 depicts a slave device consisting of an SSBIslave 1310 that is used solely for SSBI communication. FIG. 15 depicts aconfiguration in which a slave device 230, comprising an SBI slave 1220and an SSBI slave converter 1420, as depicted in FIG. 14, may also bedeployed for SSBI mode only. In this example, the SBCK input may be tiedto ground. The SBST may be tied high. This will indicate to the SSBIslave converter 1420 to remain in SSBI mode. Note that no mode pin orother selection device is needed. SSBI_DATA may then be directlyconnected to the joint SBDT/SSBI_DATA pad, and SSBI communication maythen be carried out.

FIG. 16 shows another embodiment, essentially performing the same asshown in FIG. 15. In this example, however, the pins for SBCK_IN andSBST_IN may be removed (i.e. pads 1430 and 1440 are removed, or deployedfor other purposes). Internally to slave device 230, the SBCK input toSSBI slave converter 1420 is tied low, and SBST is tied high. Thus, acombination 1-wire/3-wire slave may be designed, and with these simplemodifications, the extra pins for SBI mode are not needed. The remainingconnections are identical to those described with respect to FIG. 14.

A variety of techniques may be used to perform 1 wire to 3 wireconversion. The SSBI Slave Converter block 1420 examines the SBDT datastream and generates SBCK and SBST therefrom. Various exampleembodiments, detailed below, illustrate techniques for performing thisconversion. Among others, three issues may arise with conversion. First,the data rates of the 1-wire scheme should be matched with the 3-wirescheme. Second, a variable number of register reads and writes in onetransfer may be supported. Third, slave SBI blocks may need to beeffectively reset during a multiple access transfer.

For the first issue, if the 1-wire and 3-wire schemes adopt the samedata rate, the issue is resolved transparently. Otherwise, buffers maybe deployed to accommodate variance in the rates between the twoschemes. Those of skill in the art will recognize how to perform thecorrect buffering in various embodiments, and such buffering is notdetailed further herein. In example embodiments described below, acommon rate is shared between SBI and SSBI interfaces, although otheralternate embodiments are envisioned.

For the second issue, 3-wire SBI protocols use SBST to denote the startand end of a transfer, thus a given transfer may contain one or manyregister reads and writes. With a 1-wire bus, it is necessary to informthe slave when the last register access of a multi-access transfer iscompleted. In one embodiment, a header may be added to each transferspecifying how many register accesses to expect. This may introduceoverhead. In an alternate embodiment, a termination symbol may be sentafter the final register access is done. This also adds overhead, butthe overhead may be less than with a header. In embodiments detailedbelow, a termination symbol will be deployed to resolve the secondissue. When the termination symbol is seen by a receiver, it knows thetransfer has ended and can enter the idle state and wait for the nextstart bit. Such a termination symbol will be optionally inserted whenused for this mode of operation, specifically when interfacing with aslave that needs to support both 3-wire and 1-wire protocols. Thetermination symbol need not be deployed in alternate configurations.

A termination symbol needs to be unique from the regular data stream. Inthis example embodiment, the termination symbol is defined as a sequenceof high and low values that alternate every clock cycle for 4 cycles. Inexample embodiments detailed herein the sequence is 1 0 1 0, butalternate sequences will be apparent to those of skill in the art.Because the signal alternates each clock cycle in a terminationsequence, instead of every two clock cycles in ordinary communication,it is distinguished uniquely from anything else in the data stream.Hence, the termination sequence (“T”) may be sent at any time. Examplereceiver circuitry for detecting the termination symbol is detailedbelow with respect to FIG. 34, which illustrates the waveform on thedata line including the termination symbol.

For the third issue, a slave SSBI block waits for the termination symbolto determine when the transfer is done. Thus, it is possible for themaster and slave to get out of sync when the master goes into idle modewhile the slave is in the middle of a transfer. In such a situation, theslave remains indefinitely in this state until the end of the nexttransfer the master initiates. So, to force the slave into the idlestate more quickly, an option will be provided to arbitrarily transmittermination symbols. This technique is illustrated in detailedembodiments below.

SSBI Master

In any embodiment including an SSBI master, one or more SSBI masterblocks 1110 may be deployed. The SSBI masters 1110 may be identical, orone or more of them may be customized in some way. In this section, anexample SSBI master block 1110 is described. The ports for this exampleare detailed in Table 2. Timing diagrams for write and read proceduresare detailed in FIGS. 17 and 18, respectively. The interrelationshipbetween the clocks in a master and slave device is depicted in FIG. 19.FIGS. 20-22 detail portions of example logic suitable for deployment inthe example SSBI master 1110. It will be clear to those of skill in theart that these example embodiments serve as illustrations only, andvarious alternatives will be clear in light of the teaching herein.

An example SSBI Master may have the following properties: It may operatewith a pad (i.e. 1120) for SSBI_DATA with a keeper to ensure the signaldoes not float and a pulldown device that may be enabled (details notshown). Modifications for alternate pad configurations will be apparentto those of skill in the art. A status bit may be provided to allowsoftware to determine if the current SSBI transaction has completed ornot. For reads, the transaction may not be considered completed untilthe requesting logic or software application has read the returned data.A mode may be provided such that an SSBI command may be held off until ahardware enable signal asserts, or else takes effect immediately if theenable signal is already asserted. This may be useful when a read orwrite is to be performed at a known time. For example, measurements of aslave device may be performed when the slave device is in a consistentstate. An output signal indicating when a write has occurred may beprovided. Thus, the requesting logic or application may use theknowledge of the completed write to perform subsequent actions. This maybe useful when configuring slave devices such as RFICs that may needcalibration, for example.

The SSBI master 1110 is responsible for converting a read or writerequest into the signaling on the 1-wire SSBI bus. This block is alsoresponsible for de-serializing read register data from the SSBI bus. Anoptional SSBI arbiter block (not shown) may be deployed for arbitratingrequests from multiple controlling parties (called hosts). An arbitermay take requests from the hosts using the same signaling expected bythe SSBI master 1110. An arbiter may perform arbitration, allowing thewinner's request to go through while stalling requests from the otherhosts. Depending on the host type, different logic may be used. The SSBImaster 1110 may be used to provide an interface by which a host, i.e. amicroprocessor, can program accesses with the SSBI through software. Asystem deployed with three hosts, for example, may be deployed using thebuilding blocks of an arbiter and one or more SSBI masters, while asystem only requiring one host may be deployed without an arbiter andthe host may interface directly with the SSBI Master bus interface.

As one example of the flexibility with which embodiments may bedeployed, a hardware parameter, SSBI_DATA_WD, is defined forparameterizing various SSBI blocks. The read/write timing waveformsdescribed in FIGS. 17-19, 24-25, 28, 33-34, and related figurescorrespond to SSBI_DATA_WD=8.

FIGS. 17-22 illustrate one example SSBI master 1110 embodiment. Thisembodiment is suitable for deployment when only the native SSBI formatsneed to be supported. Various modifications may be made for variousalternate embodiments. Modifications to this embodiment are detailed forsupporting FTM transfers (an example of a legacy SBI format) over theSSBI bus are described in an alternate embodiment, detailed with respectto FIGS. 28-31, below.

As described above, one or more of various types of hosts may interfacewith an SSBI master 1110, with one or more arbiters and other interfacelogic for communication therewith. In one example embodiment, one ormore of the hosts may be a microprocessor, DSP, other general or specialpurpose processor, or any other logic deployed for such interface. Inputand output signals and/or commands are defined for clarity ofillustration below, as shown in Table 2. These input and output signalsand commands are detailed further below, along with example embodimentsfor producing or responding to them. Those of skill in the art willrecognize various alternative interface designs that may be deployed. Asvarious hosts, such as microprocessors, may have varying interfaces forperforming accesses such as writes, reads, and returning status resultsand signals, one of skill in the art may readily modify the interfaceillustrated, or determine appropriate logic for interfacing with one ormore hosts of various types. These details are omitted in the followingdiscussion for clarity. As general examples, a host may interface withan SSBI master using any combination of read, write, data, address, andother signals to generate commands and set parameters. Writing to orreading from pre-defined registers, or bit locations therein, may beused for setting parameters or issuing commands, a technique well knownin the art.

The SSBI master 1110 interfaces with the SSBI bus. It receives signalsdescribing the SSBI command to perform, then generates or monitors theserial SSBI data stream. This example SSBI master is ambivalent abouthow many entities (i.e. hosts) may initiate SSBI commands, and anydesired arbitration or muxing is dealt with external to this block. Inthis example, the SSBI master idles until it receives an access requestor other command. It then asserts an acknowledge line, performs thetransaction, and, upon completion of the access, generates a pulse on adone line, indicating that it is ready to start the next access. Forboth reads and writes, the acknowledge signal will pulse when thetransaction has been sampled and is starting. Whatever logic (i.e. host)made the request may then change the register information (address,data, etc.) to prepare for the next request and may assert the requestline again if desired. When the first access is completed, the donesignal asserts. While a write command may not require monitoring thedone signal, unless that information is useful for some portion of therequesting application, the done signal is useful for sampling thereturned data for reads.

TABLE 2 SSBI Master Port Descriptions Port Direction DescriptionSSBI_CLK Input Clock RESET Input Synchronized version of a reset signalSSBI_DATA_DEL[1:0] Input Specifies amount of delay of SSBI_DATA_IN in ½clock units IDLE_SYMS[1:0] Input Specifies minimum number of idlesymbols between back to back transfers SEL_RD_DATA[1:0] Input Specifieswhich RD_DATA value to select REQ Input Request asserts to informinterface to perform a read or write, remains high until ACK assertsREAD Input Control signal indicating a request is to perform a readADDR[7:0] Input Slave register address for transfer WR_DATA Input Writedata for slave register [SSBI_DATA_WD-1:0] OVR_VALUE Input Value to bedriven on SSBI_DATA in override mode OVR_MODE Input Control signal toenable override mode SSBI_DATA_PDEN Input Pulldown enable for SSBI_DATApad; asserted on reset; deasserted by subsequent command to carry onnormal SSBI activity SSBI_DATA_IN Input SSBI_DATA input SSBI_DATA_OUTOutput SSBI_DATA output SSBI_DATA_OE Output Output enable for SSBI_DATApad RD_DATA Output Read data returned by slave register[SSBI_DATA_WD-1:0] ACK Output Pulses when the SSBI transaction has beenaccepted and will start DONE Output Pulses when the SSBI transaction hasbeen completed; may be used to sample RD_DATA for reads STATE_INV OutputInverse of STATE signal READ_REQ_SERVED Output Set for duration readrequest is being served

Timing diagrams for writes and reads are shown separately in FIG. 17 andFIG. 18, respectively. The discussion corresponding to these figures maybe applied to the example embodiment detailed further below with respectto FIGS. 20-22. For both access types, a merged SSBI_DATA bus is showninstead of separate SSBI_DATA_IN and SSBI_DATA_OUT. In an exampleconfiguration of pad circuitry, anything on SSBI_DATA_OUT will appear onSSBI_DATA_IN. For writes, SSBI_DATA_IN will be ignored. For reads,SSBI_DATA_OUT is driven onto the SSBI_DATA pad only when SSBI_DATA_OE isasserted. The waveform for SSBI_DATA uses the notation RW to denote theread/write bit (1 is read, 0 is write, in this example), A7 to A0 forthe address bits, D7-D0 for the data bits (SSBI_DATA_WD=8), and P forthe pause bit. Note that alternate embodiments may include smaller orlarger address spaces, as well as different data widths (i.e.SSBI_DATA_WD not equal to 8).

The SSBI master resets into an Idle state (indicated on the STATE line)and remains there until it sees REQ assert. The SSBI master then samplesthe other input signals, asserts ACK, and generates the serial datastream output onto SSBI_DATA. At the end of the access, DONE is pulsedto indicate the conversion is complete. Once ACK asserts, starting inthe following clock cycle, REQ can be asserted for the next access. Thataccess will be held off until the current one completes. In thisexample, REQ, ADDR, WR_DATA (for a write) and READ will reflect theparameters for a next access until ACK asserts for that access (afterwhich the parameters may change for a subsequent access). In FIGS. 17and 18, the second access (REQ and ACK) is shown dotted. If the secondrequest is made before the first one completes, the SSBI master maystart the next transfer without any intervening idle symbols. A slaveshould not need to see a low to high transition to detect the startsymbol. It should be content to sample the start symbol without a prioridle symbol, hence the SSBI master may be designed to support thisoption. However, in this embodiment, a software programmable parameter,IDLE_SYMS, is defined to insert 1 to 3 idle symbols in between eachtransfer, as desired.

In FIG. 17, when REQ asserts, ADDR, WR_DATA and READ are sampled into ashift register (i.e. shift registers 2130 and 2140, and flip-flop 2110)along with a start bit. STATE becomes SAMPLE (1), and STB beginstoggling. STB acts as a counter enable causing BITCNT to count symbolstransmitted. All 18 bits of the transfer (the start bit+READ+ADDR+DATA)are shifted by the shift register every other clock cycle. During thesecond half of the last symbol (D0), DONE is pulsed. Another signalintroduced below, DONE_DELX (not shown in FIG. 17) may pulse at thistime as well, or it may pulse IDLE_SYMS symbol periods later. If thereis no outstanding request, DONE_DELX resets STATE to Idle (0) and theSSBI master waits for the next assertion of REQ. If there is anoutstanding request, the REQ signal is effectively observed during thesame cycle DONE_DELX asserts, causing ACK to assert in the subsequentcycle, and keeping STATE at SAMPLE (1). Such a transfer continues asdescribed for the first transfer.

FIG. 18 illustrates a read operation. The block performs the same stepsas for writes except that SSBI_DATA_OE de-asserts once A 0 has beentransmitted. The connected slave device then has control of the bus toreturn slave register data. Once the slave has returned such data, thereis another pause bit, after which the master may drive the bus again.The read bits enter a shift register (i.e. shift registers 2130 and2140), which is relatched in the cycle preceding DONE assertion. Thisperformed this way in this example to prevent RD_DATA from togglingunnecessarily, since RD_DATA may be feeding large clouds of muxing orother logic. Logic receiving RD_DATA may sample it using DONE as theenable. Subsequent requests may be handled in similar fashion as forwrites, described above.

One consideration is the time at which the SSBI master should sample theSSBI_DATA bus for the read bits. In the ideal case, the SSBI_DATA busshould appear to the master as shown in FIG. 18. There may be variousfactors at work to prevent this ideal situation though: for example,sampling uncertainty at the receiver due to blind phase detection, aswell as various delays including pad, board, and internal chip delays.

FIG. 19 illustrates these phenomena. The top waveform shows SSBI_CLK atthe SSBI master. The second pair of waveforms illustrates what SSBI_DATAlooks like at the master and slave devices assuming no delays. The thirdset of waveforms show what happens when there is ½ of an SSBI_CLK cycleof delay in each direction. The effect is that the read data may appearon SSBI_DATA at the master device one full clock period later than inthe case where there are no delays. In addition, the example slavedevice will sample the symbols somewhere between 25-75% into its clockperiod. As a result, there is uncertainty in sampling the data at theright time on the master side.

In the example embodiment, some flexibility is added in the SSBI masterto mitigate against these effects. There are two software-programmedfeatures that allow for a robust system able to handle delays up to 3clock periods.

The first feature is delaying SSBI_DATA_IN. As discussed above, thesampling uncertainty at the slave device may not be adjusted for at themaster device, assuming true blind phase detection. However, the delaysfor a given SSBI port will be relatively fixed in a given systemdeployment. As a result, if there is very little delay, the samplingpoint may be pulled in earlier. With relatively large delays, thesampling point may be pushed out. To accomplish this easily in theexample SSBI master, flexibility is added to delay the incomingSSBI_DATA_IN signal by 0, 0.5, 1 or 1.5 clock periods. Then for allcases, the delayed version of SSBI_DATA_IN will be sampled in FIG. 18 atthe end of the symbol periods. In any given deployment, other delays(including fewer or greater choices) may be used (i.e. 0.5 and 1.5cycles only).

The second feature allows control of the BITCNT cycle in which RD_DATAreturned by the slave device is captured. In FIG. 18, it is shown thatRD_DATA is available in cycle 19. However, the data may also be capturedin a cycle later then 19. The time when the SSBI master again takescontrol of the SSBI_DATA line may also be adjusted so as to give timefor RD_DATA to be ready. This feature is controlled based on theparameter SEL_RD_DATA. For example, when SEL_RD_DATA=00, the numbers inbold in FIGS. 20 and 22, detailed below, are used as shown. WhenSEL_RD_DATA=01, these numbers are incremented by 1.

These settings may be selected using a variety of techniques. Onetechnique is for the designer to carefully look at the timing andunderstand the various delays. Alternatively, a trial and error approachmay be adequate. For example, a procedure may simply read a slaveregister expecting a particular value, then adjust the setting if thevalue returned is incorrect.

FIGS. 20-22 illustrate example circuitry suitable for deployment in anexample SSBI master 1110. Various modifications and alternatives will beapparent to those of skill in the art in light of the teaching herein.The top of FIG. 20 illustrates logic for delaying SSBI_DATA_IN based onSSBI_DATA_DEL. SSBI_DATA_IN_DEL is generated as follows. SSBI_DATA isfed into flip-flops 2010 and 2030. Note that all clocked devices inFIGS. 20-22 are clocked by SSBI_CLK, or its inverse (shown with theconventional notation of a bubble in front of the clock input). Notethat flip-flop 2010 is clocked with the inverse of SSBI_CLK, andflip-flop 2030 is clocked with SSBI_CLK directly. The output offlip-flop 2010 is directed to the input of flip-flop 2020. SSBI_DATA_INis delivered to one input of mux 2040, as are the outputs of flip-flops2010-2030. SSBI_DATA_DEL is used to select one input of mux 2040 as theoutput, or SSBI_DATA_IN_DEL.

Below, in FIG. 20, is logic for generating DONE_DELX based on IDLE_SYMS.In this example, DONE_DELX is formed in logic 2050 as the AND of STB andthe OR of (NOT SREAD AND BITCNT=17+IDLE_SYMS) and (SREAD andBITCNT=19+IDLE_SYMS). Recall that numbers in bold correspond toSEL_RD_DATA=0, and the numbers may be modified for other values, asdescribed above.

FIG. 21 shows the entire shift register chain described above withrespect to FIGS. 17 and 18. Starting at the lsb, this chain is composedof a SSBI_DATA_WD bit shift register 2140, a 9-bit shift register 2130and a single register (or flip-flop) 2110 that drives SSBI_DATA_OUT. Inthis example, the one bit register 2110 is initially pre-loaded with thestart symbol. The signal REQP is used to latch the request informationinto the shift register chain. The 9-bit shift register 2130 ispre-loaded with the read/write bit and the address bits (the & indicatesconcatenation). The SSBI_DATA_WD bit shift register 2140 is pre-loadedwith write data for write operations or all 0's for read operations. The0's ensure that at the end of a read operation, a 0 ends up in the onebit register 2110 feeding SSBI_DATA_OUT, which is used for the Idlestate in this example. The signal STB is used to enable the shiftregister chain to shift. During a transfer, STB will assert every otherclock cycle (detailed further below).

The shift input to shift register 2140 is determined as the output ofmux 2150, which selects a 0 when SSBI_DATA_OE is asserted, andSSBI_DATA_IN_DEL otherwise. The parallel output of shift register 2140may be made available as RD_DATA_PRE. The shift output of shift register2140 is connected to the shift input of shift register 2130. The shiftoutput of shift register 2140 encounters additional logic in thisexample, to illustrate another optional feature. An override mode isdefined to allow the value indicated by parameter OVR_VALUE to overridethe OR 2120 of the shift output of shift register 2130 with REQP (usedin normal SSBI operation) when OVR_MODE is asserted, which, in thisexample, is selected in mux 2160. The output of mux 2160 is delivered tothe input of flip-flop 2110 (shown as a flip-flop resettable by RESET).The output of flip-flop 2110 produces SSBI_DATA_OUT.

FIG. 22 illustrates additional control logic for SSBI master 1110. OnceSTATE is 1 (the output of Set/Reset (SR) flip-flop 2220), the counter2228 for generating BITCNT is enabled. For writes, the shift registerchain (2110, 2130, and 2140) is enabled every other clock cycle untilall the data goes out, while 0's are shifted into the chain. For reads,the start symbol and address bits are shifted out, while 0's are shiftedin. However, when it is time to sample incoming read data,SSBI_DATA_IN_DEL is sampled by the SSBI_DATA_WD bit shift register 2140used for write data. Once all bits of the read data have been shiftedin, they are available on RD_DATA_PRE and relatched in register 2208 togenerate RD_DATA in the cycle before the DONE assertion. This enable isformed as the AND of SREAD, NOT STB, NOT RESET, and BITCNT=19.

STATE is generated as the output of SR flip-flop 2220. The set input toSR flip-flop 2220 is formed as the AND 2216 of REQP and NOT RESET. Thereset input to SR flip-flop 2220 is formed as the OR 2218 of DONE_DELXand RESET.

STB (also labeled as CNT_EN) is formed as the output of resettableflip-flop 2224. The input to this flip-flop is the inverse 2226 of itsoutput, thus the creation of STB alternating every clock cycle when theflip-flop is not being reset. The reset input is formed as the OR 2222of REQP and NOT STATE.

BITCNT (a 5-bit signal in this example, alternate embodiments mayprovide different parameters requiring alternate values throughout FIGS.20-22) is formed as the output of counter 2228. The reset of counter2228 is identical to the reset of flip-flop 2224. The enable of counter2228 is CNT_EN (or STB), which allows for counting during a transmissionor reception, as described above.

SREAD is formed as the output of flip-flop 2210, which is reset viasignal RESET. Flip-flop 2210 is enabled with REQP. The D input toflip-flop 2210 is READ.

In this example, a signal READ_REQ_SERVED is generated for use by otherlogic as the AND 2230 of SREAD and STATE.

REQP is formed as the AND 2204 of REQ and the OR 2202 of NOT STATE(STATE_INV) and DONE_DELX. REQP is delayed by a clock cycle in flip-flop2206 to produce ACK.

In this example, upon reset, STATE and SSBI_DATA_OUT will synchronouslyclear. SSBI_DATA_PDEN asynchronously sets causing SSBI_DATA_OE to golow. In this example, when a software application initiates some SSBIactivity, it writes to a control register, or uses some alternatesignaling technique, to reset the SSBI_DATA_PDEN bit. This changesSSBI_DATA_OE to ‘1’ and the SSBI master 1110 starts driving ‘0’ onSSBI_DATA (as detailed above). Thus, SSBI_DATA_OE is formed as the AND2214 of NOT SSBI_DATA_PDEN and the output of flip-flop 2212. Flip-flop2212 is reset with RESET. Flip-flop 2212 is enabled by STB. The D inputto flip-flop 2212 is formed by the OR of BITCNT<9, BITCNT>=19, and NOTSREAD.

Again, recall that numbers in bold correspond to SEL_RD_DATA=0, and thenumbers may be modified for other values, as described above. All theregisters in FIG. 22 are clocked with SSBI_CLK.

SSBI Slave

FIG. 23 depicts an example embodiment of SSBI slave 1310. Example SSBIslave bus interface port descriptions are detailed in Table 3. In thisexample SSBI slave bus interface 2310 is connected with slave registersblock 2320. The single wire SSBI data bus is connected with a pad (notshown), and incoming data is delivered to SSBI slave bus interface 2310on SSBI_DATA_IN. Outgoing data is delivered on SSBI_DATA_OUT, with thedirectionality of the pad controlled via SSBI_DATA_OE. The SSBI_CLKsignal is delivered as a clock to SSBI slave bus interface 2310. Slaveregisters block 2320 may also receive SSBI_CLK, but it is optional (anoptional mechanism for determining whether or not the SSBI_CLK isoperational is detailed below). Slave register accesses are made betweenSSBI slave bus interface 2310 and slave registers 2320 via the ADDR,WR_STB, WR_DATA, and RD_DATA signals. The outputs of the slave registersare delivered for use by the slave device 230. Read values from theslave device 230 are delivered to slave registers 2320 for access viathe SSBI bus.

The SSBI Slave Bus Interface 2310 is responsible for doing serial toparallel conversion on the 1-wire bus signal and converting it into aread or write request. This request is sent to slave registers block2320, which contains the write registers and is responsible for muxingread registers. This example configuration is one embodiment that hasthe advantage that the SSBI slave bus interface 2310 may be designed tobe identical for various slave designs, while logic that is particularto a slave is deployed in slave registers block 2320. Variousalternatives may also be deployed.

SSBI slave bus interface 2310 examines the SSBI_DATA line for the startsymbol, which denotes the start of a transfer. It then looks at thefirst symbol to determine if it is a read or write, then scans in theaddress bits. Once all the address bits are scanned in, they are fed outas ADDR to the slave registers block 2320. For a write, the data bitsare shifted in and then fed as WR_DATA to the slave registers block 2320along with a strobe, WR_STB. WR_STB is used by the slave registers block2320 to sample the address (ADDR) and data (WR_DATA) fields. For a read,after ADDR is passed to the slave registers block 2320, during the pausebit the SSBI read register data (RD_DATA) is sampled by the SSBI slavebus interface 2310 and then shifted out bit by bit onto the SSBI bus.Once a single transaction is complete, the SSBI slave bus interface 2310awaits the next start bit.

In this example, multiple transactions terminated with a terminationsymbol (such as BTM, described above) are disallowed. This configurationprovides simplified design (less hardware, fewer cases to test), and issuitable for deployment when there is little advantage to allowingmultiple transfers, i.e. the overhead for an individual transfer isrelatively small. Alternate embodiments may allow for multipletransactions terminated with a termination symbol.

In alternate embodiments, other versions of the SSBI slave bus interface2310 may be deployed. One difference may be in the number of outputports. A configuration may have one set of ADDR, WR_STB, WR_DATA, andRD_DATA, or additional sets of these signals. By including additionalsets, multiple banks of read and/or write registers may be accessedindependently. Another option is to have either a bidirectional databusor separate buses for read and write data. Various other alternativeswill be apparent to those of skill in the art. For clarity ofdiscussion, the example embodiments detailed below will comprise asingle set of ADDR, WR_STB, WR_DATA, and RD_DATA, with separate busesfor read and write data.

TABLE 3 SSBI Slave Bus Interface Port Descriptions Port DirectionDescription SSBI_CLK Input Clock RESET Input Synchronized version of areset signal SSBI_DATA_IN Input SSBI_DATA input from chip padSSBI_DATA_OUT Output SSBI_DATA output to chip pad SSBI_DATA_OE OutputOutput enable for SSBI_DATA pad ADDR[7:0] Output Latched SSBI addressWR_STB Output Write strobe; May be used as clock for SSBI writeregisters WR_DATA Output Latched SSBI register write data Port DirectionDescription [SSBI_DATA_WD-1:0] RD_DATA Input Muxed SSBI register readdata; sampled before [SSBI_DATA_WD-1:0] ADDR changes TCXO_DIS Input ‘0’in normal operation; ‘1’ when SSBI_CLK is off; may be stored in a slaveregister RESET_TCXO_DIS Output Used to reset TCXO_DIS register bit

Writes and reads are shown separately in FIG. 24 and FIG. 25,respectively. The discussion corresponding to these figures may beapplied to the example embodiment detailed further below with respect toFIGS. 26-27. The read/write timing is described for the case whenSSBI_DATA_WD is 8. Alternatives for SSBI_DATA_WD are described withrespect to FIGS. 26-27. For both access types, a merged SSBI_DATA bus isshown instead of separate SSBI_DATA_IN and SSBI_DATA_OUT. In an exampleconfiguration of pad circuitry, anything on SSBI_DATA_OUT will appear onSSBI_DATA_IN. For writes, SSBI_DATA_IN will be ignored. For reads,SSBI_DATA_OUT is driven onto the SSBI_DATA pad only when SSBI_DATA_OE isasserted. The waveform for SSBI_DATA uses the notation RW to denote theread/write bit (1 is read, 0 is write, in this example), A7-A 0 for theaddress bits, D7-D0 for the data bits, and P for the pause bit. Notethat alternate embodiments may include smaller or larger address spaces,as well as different data widths (i.e. SSBI_DATA_WD not equal to 8).

In FIG. 24, when the start bit is found, FOUND_ST goes high. It isgenerated through logic that, when STATE is Idle (0), simply samplesSSBI_DATA every clock cycle until a high is found. FOUND_ST is generateda half clock cycle later to allow for metastability resolution. FOUND_STcauses STATE to become Sample (1), which in turn allows STB to toggle.STB, in turn, causes BITCNT to increment. STB is used as an enable tosample the symbols into the shift register (i.e. 2628). The shiftregister has a number of bits indicated by INPUT_DATA_SIZE. Thisconstant has a value that is the larger of 8 or SSBI_DATA_WD. BITCNT(i.e. 2646) keeps track of how many bits have been sampled. Once all theaddress bits are latched in (denoted by BITCNT=8), the contents of theshift register are relatched (i.e. 2634) and output onto ADDR. Thisrelatching is optional, the purpose of which is to conserve power in theSlave registers block, since ADDR will potentially feed a reasonablylarge amount of mux logic. Similarly, once all the data bits are latchedin (denoted by BITCNT=16), the contents of the shift register arerelatched (i.e. 2636) and output onto WR_DATA. WR_STB is pulsed so theslave registers block 2320 knows to perform the write. DONE asserts whenBITCNT=17, to reset STATE to Idle (0), so the process may repeat ifneeded.

FIG. 25 illustrates a read operation. The block performs the same stepsas for writes through to outputting the address on ADDR. Not shown inthe previous figure, RD_DATA may be muxed based on ADDR, so even forwrites, RD_DATA may potentially change when ADDR changes, even though itis ignored. During the BITCNT=9 cycle, RD_DATA is sampled into a shiftregister (i.e. 2660), and shifted bit by bit onto the SSBI_DATA_OUTline. SSBI_DATA_OE asserts to indicate when to drive data onto theSSBI_DATA pad and remains high until all the data has been shifted ontothe bus. DONE asserts when BITCNT=19, to reset STATE to Idle, so theprocess may repeat if needed.

Note that read data is output a full clock cycle early (½ a symbolperiod). This reduces the effectiveness of the pause bit between theaddress and read data. In this case, there is one clock cycle ofnonoverlap time. An advantage of this approach is that if SSBI read datais shifted out when SSBI write data would be seen, from the point ofview of the master, the read data will appear late due to the round tripdelay. By outputting the read data early, it will be offset by the roundtrip delay, making it appear closer to when the master really expects tosee it.

Because of blind phase detection, there is no guarantee that SSBI_CLKwill be lined up with SSBI_DATA as shown in the figures. The figuresshow SSBI_CLK at one extreme, perhaps the “best case”. The “worst case”will be such that the start bit is found one full clock cycle later,resulting in all the signals (except SSBI_DATA) being shifted to theright by one clock cycle. This does not introduce a problem. Instead ofsampling the symbols 25% into the symbol period, they will be sampled75% into the symbol period. For reads, instead of driving SBI read data½ symbol period early, it will be ½ symbol period late. This one cycleof variability is reduced to half a cycle, by using the LATE signal. Itis generated by the circuit similar to the one for FOUND_ST (bothdetailed further below), except that it works on opposite clock edges.When LATE is 0, SSBI_DATA_OUT and SSBI_DATA_OE are delayed by half aclock cycle before being used. When LATE is 1, they are used as is. Thecircuitry associated with the LATE signal also exists for the SSBI slaveconverter 1420, introduced above and detailed further below with respectto FIGS. 32-35.

Another optional feature may be included such that the master device 220may disable the slave clock by setting some slave register bit, denotedhere as TCXO_DIS. When this bit is set, the slave SSBI_CLK will turnoff. To enable the clock again, the master device transmits the sequence0 to 1 to 0 to the slave. This is captured by the slave, which generatesthe RESET_TCXO_DIS signal. This signal resets TCXO_DIS, which in turnagain enables the SSBI_CLK for the slave. This feature allows the masterto put the SBI slave device in sleep mode and hence saves power(detailed further below).

FIG. 26 illustrates example circuitry suitable for deployment in anexample SSBI slave bus interface 2310. Various alternatives for thecontrol mechanisms shown may be deployed, using any combination oflogic, state machines, microcode, software, and the like. In thisexample, BITCNT denotes the various states required. Note that thecontrol signals depend on SSBI_DATA_WD, and may change in accordancewith changes thereon.

The parameter INPUT_DATA_SIZE is computed as the maximum 2614 of 8 andSSBI_DATA_WD. In the example embodiment, both parameters are knownapriori and used to generate a specific logic configuration for theselected SSBI_DATA_WD parameter. An alternate embodiment may be deployedto accommodate programmable values for SSBI_DATA_WD. Thus, for example,the bit selections for the inputs to registers 2632-36 may include logicbefore and after to accommodate programming changes. Another option isto have a programmable ADDR size, with similar changes for accommodatingdifferent values of ADDR. These details are not shown. Those of skill inthe art will readily adapt these and other options in light of theteaching herein. For clarity of discussion, the following assumes a setSSBI_DATA_WD and INPUT_DATA_SIZE for a given deployment.

Note that all clocked devices in FIG. 26 are clocked by SSBI_CLK, or itsinverse (shown with the conventional notation of a bubble in front ofthe clock input). Unless otherwise noted, the registers detailed beloware clocked by SSBI_CLK.

In this example, locating the start bit is performed as follows.SSBI_DATA_IN is latched by flip-flop 2602 with inverted SSBI_CLK and byflip-flop 2610 with SSBI_CLK. The output of flip-flop 2602 is latched byflip-flop 2604 with SSBI_CLK to produce FOUND_ST_N. The output offlip-flop 2610 is latched by flip-flop 2612 with inverted SSBI_CLK toproduce FOUND_ST. All four flip flops are reset by the OR (2606, 2608)of STATE and RESET_EFF. FOUND_STN is latched by flip-flop 2618 toproduce LATE, enabled by the AND 2616 of FOUND_ST and NOT STATE.FOUND_ST is latched by flip-flop 2622 to produce STATE, clocked by theinverse of SSBI_CLK. Flip-flop 2622 is asynchronously reset byRESET_EFF. The enable for flip-flop 2622 is determined by the output ofmux 2620, which selects DONE when STATE is asserted and FOUND_STotherwise.

DONE is determined as the AND 2626 of STB and the OR 2624 of two inputs.The first input to OR 2624 is the AND of NOT READ andBITCNT=9+SSBI_DATA_WD. The second input to OR 2624 is the AND of READand BITCNT=11+SSBI_DATA_WD. SSBI_DATA_IN is shifted into shift register2628 with the inverse of SSBI_CLK, enabled by the AND 2630 of NOT STBand STATE. The parallel output of shift register 2628 is of sizeINPUT_DATA_SIZE. The least significant output bit is latched in register2632, enabled by the AND of STB and BITCNT=1, to produce READ. The 8least significant output bits are latched in register 2634 to produceADDR, enabled by the AND of STB and BITCNT=9. The output bitsSSBI_DATA_WD-1 to 0 are latched in register 2636 to produce WR_DATA,enabled by the AND of NOT READ, STB, and BITCNT=9+SSBI_DATA_WD. Thisenable signal is also latched in register 2638 to produce WR_STB,asynchronously reset by RESET_EFF.

STB is formed as the output of flip-flop 2640, taking its input as NOTSTB, and reset by NOT STATE. NOT STB is formed by inverter 2644inverting STB. NOT STB is latched in flip-flop 2642 to produce NOTSTB_D. The output of counter 2646 forms BITCNT, which is reset by the ORof NOT STATE and DONE, and enabled by STB.

The optional clock disabling circuit, described above, is implemented inthis example as follows. TCXO_DIS is latched in flip-flop 2648, clockedby SSBI_DATA_IN. The output of flip-flop 2648 is latched by flip-flop2650 to produce RESET_TCXO_DIS, which is clocked by NOT SSBI_DATA_IN.Both flip-flops are reset asynchronously by RESET.

RESET_EFF is formed as the output of flip-flop 2672, the input of whichis the output of flip-flop 2670. The input to flip-flop 2670 is theoutput of flip-flop 2668, which takes a ‘0’ as its input. All threeflip-flops are asynchronously set by the OR 2666 of TCXO_DIS and RESET.

SSBI_DATA_OUT is selected via mux 2664 as the shift output of shiftregister 2660 when LATE is asserted. SSBI_DATA_OUT is selected via mux2664 as the output of flip-flop 2662 when LATE is not asserted.Flip-flop 2662 takes as its input the shift output of shift register2660, clocked by the inverse of SSBI_CLK. The parallel input to shiftregister 2660 is the SSBI_DATA_WD wide RD_DATA input. The shift input toshift register 2660 is a ‘0’. Shift register 2660 is loaded by the ANDof READ, NOT STB, and BITCNT=9. Shifting of shift register 2660 isenabled by the AND 2658 of NOT STB_D, READ, and SSBI_DATA_OE_REG.

SSBI_DATA_OE is selected via mux 2656 as SSBI_DATA_OE_REG when LATE isasserted. SSBI_DATA_OE is selected via mux 2656 as the output offlip-flop 2654 when LATE is not asserted. Flip-flop 2654 takes as itsinput SSBI_DATA_OE_REG, clocked by the inverse of SSBI_CLK.SSBI_DATA_OE_REG is formed as the output of flip-flop 2652. The input toflip-flop 2652 is the AND of READ, BITCNT>=10, andBITCNT<=(9+SSBI_DATA_WD). Flip-flop 2652 is enabled by STB, andasynchronously reset by RESET_EFF.

FIG. 27 depicts example logic suitable for deployment as slave registersblock 2320. In this example, SSBI_DATA_WD is set to 8 for illustrativepurposes. Register 2710 is an example register for storing an outputWR_REGxxx_DATA. It receives WR_DATA as its input, which may be clockedby WR_STB. Many write registers may be deployed, and xxx may besubstituted with an appropriate identifier. Note that for a particularaddress, not all of the WR_DATA bits may need to be latched, and thusthe corresponding storage elements may be eliminated. An enable signalfor each register 2710 may be enabled according to the correspondingaddress, controlled by ADDR (details not shown). In an alternateembodiment, SSBI_CLK may be used as the clock, with WR_STB incorporatedin an enable signal. The various WR_REGxxx_DATA outputs may be deliveredto the slave device 230, as desired.

RD_DATA is formed, in this example, by the output of mux logic 2720,selected in accordance with ADDR. Various mux implementations may bedeployed, such as traditional multiplexers, combinatorial logic,tri-state bus techniques, and the like. The inputs to mux 2720 are ninput signals denoted RDREG0_DATA-RDREGn_DATA, and are assignedaccording to the corresponding address designations. These inputs maycome from anywhere within the slave device 230, as desired.

SSBI Master Supporting FTM

This section illustrates an example embodiment of an SSBI master 1110adapted to support SBI FTM mode, detailed above. FIGS. 28-31, and theircorresponding descriptions, detail the changes required in the exampleSSBI Master described with respect to FIGS. 20-22, above, to support FTMcommands over a single wire bus. This SSBI master 1110 is capable ofsupporting both SSBI Commands and FTM commands (the mode selected basedon a configuration bit called FTM_MODE). Table 4 shows additional portsfor this example embodiment, which may be combined with the ports ofTable 2.

TABLE 4 Modified SSBI Master Port Descriptions Port DirectionDescription DISABLE_TERM_SYM Input In FTM mode, when set, will suppressthe termination symbol from being sent to the Slave at the end oftransfer SEND_TERM_SYM Input In FTM mode, pulses to send just thetermination symbol to the Slave FTM_MODE Input FTM mode enable bitSLAVE_ID[5:0] Input Input Slave ID

The signal FTM_MODE, when set, indicates an access will be in FTM mode.For non-FTM mode accesses, the waveforms and circuit may be similar tothe non-modified circuit, described above with respect to FIGS. 17-22.At a high level, to support FTM mode, the following changes need to bemade: First, the command format will match FTM mode for 3-wire mode.Second, the circuit needs to identify when a burst of transfers iscompleted so it can send a termination symbol. Third, IDLE_SYMS willspecify the number of idle symbols in between two bursts, rather thanbetween individual accesses.

To simplify the following description, the term access will be used torefer to an individual read or write. The term burst will be used torefer to a sequence where a slave ID is transmitted, followed by one ormore accesses, then terminated by transmitting a termination symbol.Alternate embodiments may implement alternatives to the terminationsymbol, examples of which are given above. Thus, a burst may have oneaccess or several. Note that in non-FTM mode, there are no bursts. Allaccesses are treated as single accesses.

For a burst, the first access is preceded with the transmission of thestart bit, mode bits and slave ID. Subsequent accesses may be madewithout these transmissions. A signal CONT is defined, an example ofwhich is detailed in FIG. 31 (as the output of flip-flop 3110), and isused to denote whether an access is the first access (0) or a lateraccess (1). CONT asserts in the same cycle that REQP would assert forthe second access and will remain asserted until the termination symbolis sent. In this way, CONT may be used to configure the shift chaincorrectly to bypass the start bit, mode bits and slave ID (detailedfurther below).

As the first access completes, CONT asserts and DONE pulses. REQ may beexamined while DONE is high to determine if there is a subsequent accessin this burst. If so, ACK pulses, the new parameters are latched intothe scan chain as normal, except that the scan chain will be configuredto bypass the mode bits and slave ID. Also, BITCNT will be pre-loadedwith 10 instead of 0, since the start bit, mode bits, slave ID and firstpause bit are skipped. DONE asserts for each access as it completes.

At the end of a burst (whether it includes one transfer or a bunch oftransfers), a termination symbol needs to be output. TERM asserts forthe duration the termination symbol is sent. During this time, BITCNTneeds to increment every cycle instead of every other cycle and thepattern output is 1010. Alternate embodiments may utilize alternatetermination symbol patterns. Once the termination symbol has been sent,an internal “done” signal, DONE_DELX, needs to be generated and delayedaccording to IDLE_SYMS such that the next burst can start whenavailable. FIG. 28 illustrates the waveforms showing the end of anexample burst. Note that, in this example embodiment, STB pulses twiceduring the termination symbol, although it may be ignored by the circuit(detailed further below).

FIGS. 29-31 illustrate example circuitry suitable for deployment in anexample SSBI master 1110, modified to support FTM mode. Various othermodifications and alternatives will be apparent to those of skill in theart in light of the teaching herein.

FIG. 29 illustrates the modified logic dependent on the configurationparameters. SSBI_DATA_IN_DEL generation is the same as in the originalcircuit. DONE_DELX generation differs based on FTM_MODE. In FTM_MODE,this signal pulses at the end of a burst. Since at that time, BITCNTincrements every clock cycle, STB can be ignored.

As in FIG. 20, the top of FIG. 29 illustrates logic for delayingSSBI_DATA_IN based on SSBI_DATA_DEL. SSBI_DATA_IN_DEL is generated justas in FIG. 20. SSBI_DATA is fed into flip-flops 2010 and 2030. Note thatall clocked devices in FIGS. 20-22 are clocked by SSBI_CLK, or itsinverse (shown with the conventional notation of a bubble in front ofthe clock input). Note that flip-flop 2010 is clocked with the inverseof SSBI_CLK, and flip-flop 2030 is clocked with SSBI_CLK directly. Theoutput of flip-flop 2010 is directed to the input of flip-flop 2020.SSBI_DATA_IN is delivered to one input of mux 2040, as are the outputsof flip-flops 2010-2030. SSBI_DATA_DEL is used to select one input ofmux 2040 as the output, or SSBI_DATA_IN_DEL.

Again, DONE_DELX is based on IDLE_SYMS. As in FIG. 20, logic 2050produces AND of STB and the OR of (NOT SREAD AND BITCNT=17+IDLE_SYMS)and (SREAD and BITCNT=19+IDLE_SYMS). Mux 2910 is added to produceDONE_DELX. DONE_DELX is selected as the output of logic 2050 whenFTM_MODE is not asserted, and as BITCNT=31+IDLE_SYMS when FTM_MODE isasserted. Recall that numbers in bold correspond to SEL_RD_DATA=0, andthe numbers may be modified for other values, as described above. Asbefore, for simplicity, all the numbers correspond to the case whenSSBI_DATA_WD=8.

Most of the modifications to the logic design pertain to the shiftregister chain, which are shown in FIG. 30. This chain is extended suchthat it can store the mode bits (01) and SLAVE_ID, along with pausebits, which are present after every set of 8 bits. These additionalpause bits are treated as transmissions (the data values themselves areirrelevant) as opposed to tri-stating the bus (like a prior art SBIblock may have done). There is no longer a need to tri-state the busevery 8 symbol periods.

This example modified shift register chain is broken up as follows.SSBI_DATA_OUT is still produced as the output of register 2110, which isused to hold the start bit for the first access of a burst or READ forsubsequent accesses of a burst. Register 2110 is still reset with RESET.The enable is modified from FIG. 21, and is formed as the OR of REQP,STB, OVR_MODE, TERM and EN_TERM_CNT. The modification is the addition ofthe TERM and EN_TERM_CNT signals into the OR logic. The input is takenfrom mux 3004 (compared with mux 2160 in FIG. 21), and is used to selectshift values based on the mode, detailed further below.

Two shift registers 3014 and 3016 are deployed which are 8 and 2 bitswide, respectively. The 8-bit shift register 3014 stores the mode bits(01) and SLAVE_ID. The 2-bit shift register 3016 stores the pause bitand READ bit for the first access in FTM_MODE, or stores the READ bitand address bit 7 when not in FTM_MODE. This input is labeledSHIFT2LDVAL, which is formed as the output of mux 3028, detailed furtherbelow. The 7-bit shift register 3018 stores the lower 7 bits of theaddress (recall that in the SBI protocol, only 7 bits of address areused). Note that shift registers 3016 and 3018 take the place of shiftregister 2130 (shown in FIG. 21) when not in FTM mode. The three shiftregisters form a single chain, in that the shift output of shiftregister 3018 is connected to the shift input of shift register 3016,and the shift output of shift register 3016 is connected to the shiftinput of shift register 3014. All three shift registers 3014-3108 areenabled with STB, and loaded with REQP.

Shift register 2140 is identical to FIG. 21. The SSBI_DATA_WD bit shiftregister 2140 is pre-loaded with write data for write operations or all0's for read operations. The shift input to shift register 2140 isdetermined as the output of mux 2150, which selects a 0 whenSSBI_DATA_OE is asserted, and SSBI_DATA_IN_DEL otherwise. The paralleloutput of shift register 2140 may be made available as RD_DATA_PRE. Aswith the other shift registers, shift register 2140 is loaded with REQPand enabled with STB.

Register 3022 is added for use in FTM_MODE to store a pause bit.Register 3022 is reset by REQP. The final pause bit for FTM mode isn'tdirectly stored, but is shifted in to register 3022 from the shiftoutput of shift register 2140.

Since this SSBI master supports normal SSBI mode accesses as well as FTMmode, various muxes are used to either select or bypass additional bitsrequired for FTM mode. Additionally, in FTM_MODE, extra logic is used tobypass the mode bits, slave ID, and pause bit during the second andadditional accesses of a burst, in accordance with the signal CONT.

Mux 3020 is used to select the output of register 3022 as the shiftinput to shift register 3018 when in FTM mode. Otherwise, register 3022is bypassed, and the output of shift register 2140 is selected.

SHIFT2LDVAL is produced as the output of mux 3028. In FTM mode, READ isconcatenated to form the 2-bit value. Otherwise, READ is concatenatedwith ADDR(7) (as in FIG. 21) to form the 2-bit value.

Mux 3010 is selectable with FTM_MODE to bypass or include shift register3014 in the shift chain. In FTM mode, the shift out of shift register3014 is selected. In non-FTM mode, the output of shift register 3016 isselected. The output of mux 3010 is delivered to OR gate 2120, alongwith REQP, as described with respect to FIG. 21. The output of OR gate2120 is the bitstream for normal SSBI operation, and for the firstaccess in FTM mode (not including the termination portion of the access,when applicable).

Mux 3006 selects various bitstreams depending on the current mode. Theselect line is formed as the concatenation of TERM and CONT (shown asTERM & CONT). In SSBI mode, TERM and CONT will always be deasserted, sothe output of OR gate 2120 is selected. The output of OR gate 2120 isalso selected in FTM mode for the first access, in which case thetermination symbol is not yet to be sent (TERM is not asserted) and acontinuing access is not in progress (CONT is not asserted).

Prior to termination, and during second and subsequent accesses, CONTwill be asserted, so mux 3006 will select the output of mux 3012. Mux3012 is used for FTM mode, and may be used to bypass the mode bits,slave ID, and pause bit during the second and additional accesses of aburst. When REQP is asserted, READ is selected as the output of mux3012, otherwise the shift output of shift register 3018 is selected.

Since, in this example, the termination symbol toggles every clockcycle, the termination symbol is formed by inserting the terminationsymbol bits cycle-by-cycle into the final register 2110 feedingSSBI_DATA_OUT. TERM is used to identify when the termination symbol issent. This is implemented by feeding NOT CNT_EN into register 2110 as ittoggles every cycle (using the inverse of CNT_EN as the input allows theoutput of register 2110 to be in-phase with CNT_EN). As described above,register 2110 is enabled every clock cycle, due to the TERM signal inthe OR logic feeding the enable.

In this example, there are two special cases regarding the terminationsymbol. First, to suppress sending a termination symbol to slave,DISABLE_TERM_SYM may be asserted. One example for using this feature isto stop slave SSBI_CLK by writing to the slave register bit, TCXO_DIS,as described above. After the write completes, there should be noactivity on SSBI_DATA until the time the slave clock is to be enabledagain. After this special access, DISABLE_TERM_SYM may be used to blockNOT CNT_EN from being sent to final register 2110 feeding SSBI_DATA_OUT.Thus, when TERM is enabled, mux 3006 selects the AND of NOT CNT_EN andNOT DISABLE_TERM_SYM.

In the second case, an option is provided to send a termination symbolwithout any prior access. This is achieved by asserting SEND_TERM_SYM.This may be useful when the SSBI master 1110 is reset in the middle of atransfer, for example. In such a situation, to avoid the SBI slave beingstuck in an infinite FTM loop, the master may send a termination symbolto return the slave to Idle mode again. To enable this second feature,mux 3004 is deployed to select the input for register 2110. As in FIG.21, OVR_MODE is used to select OVR_VALUE to allow for direct control ofthe shift chain. When OVR_MODE is not asserted, an assertion ofEN_TERM_CNT selects NOT TERM_CNT(0) as the output of mux 3004.Generation of TERM_CNT is detailed below. When neither OVR_MODE norEN_TERM_CNT are asserted, the output of mux 3006 is selected for inputto register 2110.

FIG. 31 illustrates additional control logic for SSBI master 1110,modified to support FTM mode. Compare this example with the exampledescribed with respect to FIG. 22. This logic performs all the samefunctions as the earlier embodiment, with the following modifications.

As before, REQP is formed as the output of AND 2204, with REQ as one ofthe inputs. For REQP generation, DONE is added so that multiple accessescan be acknowledged within a burst. REQP is latched in flip flop 2206 toproduce ACK. The other input to AND 2204 is generated as the OR 3102 ofNOT STATE, the AND of DONE and FTM_MODE, and the AND of DONE_DELX andNOT FTM_MODE. Compare this logic with the logic of OR 2202 in FIG. 22.

As before, RD_DATA is generated as the output of register 2208, whichtakes RD_DATA_PRE as its input. The enable term is modified to includean additional term for FTM mode. The enable is formed by the AND ofSREAD, NOT STB, NOT RESET, and BITCNT=19/26. The notation BITCNT=19/26translates to: when FTM_MODE=0, look for BITCNT=19; when FTM_MODE=1,look for BITCNT=26.

In FTM mode, DONE generation occurs using a later BITCNT that is notSREAD dependent, as reads and writes in FTM mode take the same amount oftime. This is implemented in this example with mux 3114. The select linefor mux 3114 is FTM_MODE & SREAD. When FTM_MODE is asserted, the outputof mux 3114 is BITCNT=27 when SREAD is not asserted and BITCNT=27otherwise. When FTM_MODE is not asserted, and SREAD is not asserted, theoutput of mux 3114 is formed as the AND of NOT SREAD andBITCNT=(17+IDLE_SYMS). When FTM_MODE is not asserted, and SREAD isasserted, the output of mux 3114 is given as the AND of SREAD andBITCNT=(19+IDLE_SYMS). DONE is formed as the output of register 3118,which takes as its input the AND 3116 of NOT STB and the output of mux3114, and is reset with RESET.

Logic is added to generate CONT and TERM, which are all 0 when FTM_MODEis 0. CONT is set to one during the same cycle for which DONE assertsand will clear when DONE_DELX_FTM pulses. CONT is formed as the outputof register 3110. This register is set when BITCNT=27, and reset withthe OR of DONE_DELX_FTM, RESET, or NOT FTM_MODE. (DONE_DELX_FTM will beeither DONE_DELX_FTM_WR or DONE_DELX_FTM_RD depending on whether a writeor read is being performed. DONE_DELX_FTM_WR is given byBITCNT=31+IDLE_SYMS, and DONE_DELX_FTM_RD is given by 23+IDLE_SYMS.)

TERM is used to force BITCNT to increment every clock cycle during thetermination symbol. TERM is formed as the output of mux 3150, which usesSREAD as its select line. When SREAD is asserted, TERM_READ is selected,otherwise TERM_WRITE is selected. TERM_READ is formed as the AND ofFTM_MODE, BITCNT>=28, and BITCNT<=31. TERM_WRITE is formed by the AND ofFTM_MODE, BITCNT>=27, and BITCNT<=31.

SREAD, STATE, CNT_EN, and STB are generated the same as in FIG. 22.SREAD is formed as the output of register 2210, with READ as the inputand REQP as the enable. STATE is generated as the output of SR flip-flop2220. The set input to SR flip-flop 2220 is formed as the AND 2216 ofREQP and NOT RESET. The reset input to SR flip-flop 2220 is formed asthe OR 2218 of DONE_DELX and RESET.

STB (also labeled as CNT_EN) is formed as the output of resettableflip-flop 2224. The input to this flip-flop is the inverse of itsoutput, thus the creation of STB alternating every clock cycle when theflip-flop is not being reset. The reset input, CNT_RES, is formed as theOR 2222 of REQP and NOT STATE.

BITCNT (a 6-bit signal in this example, alternate embodiments mayprovide different parameters requiring alternate values throughout FIGS.29-31) is formed as the output of counter 3140 (compare with counter2228 in FIG. 22). The enable of counter 3140 is the OR 3138 of CNT_EN(or STB) and TERM. In contrast with example of FIG. 22, in this example,the width of BITCNT is increased by 1 bit since with IDLE_SYMS>0 orSSBI_DATA_WD>8, BITCNT may count past 31. The load value for BITCNT isnow dependent on whether or not the access is the first of a burst. Assuch, CONT is used as the select line for mux 3112, which, whenasserted, selects 001010 as the value of BITCNT_LDVAL, and 000000otherwise.

TERM_CNT, which is used to form the termination symbol whenSEND_TERM_SYM is asserted, as described above, is formed as follows.EN_TERM_CNT is formed as the output of SR flip-flop 3144. The set inputasserts EN_TERM_CNT when SEND_TERM_SYM is asserted. EN_TERM_CNT isdeasserted when the termination symbol is completed, as indicated byTERM_CO. The reset for flip-flop 3144 is thus the OR 3142 of RESET andTERM_CO. TERM_CNT is a 2-bit signal in this example, although othertermination symbols of various other sizes and waveforms may be deployedwithin the scope of the present invention. TERM_CNT is formed as theoutput of counter 3148, whose carryout is assigned to TERM_CO. Counter3148 is always enabled, except when reset by the OR 3146 of RESET andNOT EN_TERM_CNT. Thus, when EN_TERM_CNT asserts, the reset to counter3148 is deasserted, which causes the counter to count until the carryoutTERM_CO asserts, in turn deasserting ENTERM_CNT.

Recall that an SSBI master 1110 does not use a slave ID for SSBI mode,although slave IDs may be required for SBI mode. Since the slave devicewill decode the slave ID, it needs to be specified by themicroprocessor, or other host device, through a control register, orother techniques well known in the art. This slave ID field may beoutput to the SSBI master 1110 for each transaction. Note that, unlikewith SBI, this field may be programmed just once and never needs tochange, when a single slave is connected to an SSBI port. In addition,FTM_MODE specifies whether the transfer should be done in FTM mode ornot which allows the same SSBI master 1110 to be used with true 1-wireslaves as well as 1-wire slaves that use an SSBI to SBI converter block,such as block 1420, detailed further below.

SSBI Slave Supporting FTM

For a slave device that needs to support the 3-wire bus and 1-wire bus,one approach is to design the slave to retain a 3-wire SBI support block1220 as shown in FIG. 14, and to add an SSBI slave converter 1420 thatallows it to interface to a 1-wire bus. The SSBI slave converter block1420 may be used to convert 1-wire signaling to generate the SBST andSBCK signals and feed those to the existing 3-wire SBI slave circuitry1220. Thus, for this example, in 1-wire mode, FTM commands must be used,as SSBI commands would not be properly interpreted by the 3-wire slavecircuitry 1220. Table 5 includes port descriptions for an example SSBIslave converter 1420.

TABLE 5 SSBI Slave Converter Port Descriptions Port DirectionDescription SSBI_CLK Input Clock RESET Input Async input. This blockwill stretch it until TCXO turns on. SBST_IN Input SBST input from chippad. SBCK_IN Input SBCK input from chip pad. SSBI_DATA InputSSBI_DATA/SBDT input from chip pad. SBST_OUT Output 3-wire SBST signalgoing to SBI Slave block. SBCK_OUT Output 3-wire SBCK signal going toSBI Slave block. SBDT_PO_IN Input 3-wire SBDT, PO signal coming from SBISlave block. SBDT_OE_IN Input 3-wire SBDT, OE signal coming from SBISlave block. SBDT_PO_OUT Output 3-wire SBDT, PO signal going to chippad. SBDT_OE_OUT Output 3-wire SBDT, OE signal going to chip pad.SSBI_MODE Output SBCK_IN and SBST_IN indicating that the slave is in1-wire mode. TCXO_DIS Input It comes from slave register block. It is‘0’ is normal operation, ‘1’ when SSBI_CLK is off. RESET_TCXO_DIS OutputIt goes to slave register block to reset TCXO_DIS register bit.

An example SSBI slave converter 1420 may be used for converting SSBIsignaling into SBI signaling when in 1-wire mode, or bypassing suchconversion when in 3-wire mode. Specifically, SSBI slave converter takesin the SSBI_DATA line, among others, and generates the SBCK and SBSTsignals for a standard 3-wire SBI slave block. In this example, SBDTdoes not need to be generated in SSBI slave converter 1420, as it is maybe directly connected between the pad and 3-wire slave block, asdescribed above with respect to FIG. 14.

The SBST and SBCK inputs may be used to determine if 1-wire or 3-wireoperation is desired. 1-wire mode is selected when SBST=1 and SBCK=0, assuch a combination never occurs during normal 3-wire transfers. Thisoption for selecting the mode avoids the need for a dedicated modeselection pin or register. If 3-wire mode is selected, then the SBST andSBCK signals are muxed through to the outputs of this block, as detailedfurther below.

In 1-wire mode, the SSBI slave converter block 1420 examines theSSBI_DATA line for the start symbol, which is used to assert SBST andstart SBCK toggling. The SSBI slave converter block 1420 also looks forthe termination symbol, which is used to de-assert SBST and halt SBCKtoggling. Write data goes directly to the SBI slave block, and,similarly, read data is returned directly onto SBDT. An exampleembodiment illustrating these features is detailed below with respect toFIGS. 32-35.

FIG. 32 illustrates a portion of SSBI slave converter 1420. Thecircuitry shown is responsible for determining whether the mode is1-wire or 3-wire. SSBI_MODE goes high for 1-wire mode when SBCK=0 whileSBST=1, as shown by the AND 3250 of SBST_IN and NOT SBCK_IN. SSBI_MODEis delivered as an output, in this example, in case other functions orblocks operate in accordance with the selected mode. SSBI_MODE is alsoused to control muxes 3260 and 3270. When in 3-wire mode, i.e. SSBI_MODEis not asserted, the SBCK and SBST pad inputs (SBST_IN and SBCK_IN,respectively) are selected for output to SBST_OUT and SBCK_OUT,respectively. When in 1-wire mode, i.e. SSBI_MODE is asserted, muxes3260 and 3270 select SBST_GEN and SBCK_GEN to be output on SBST_OUT andSBCK_OUT, respectively.

RESET_EFF is a stretched reset signal, generated so that it is a minimumof two clock cycles. This ensures that RESET_EFF will be eventually seenby the circuitry even if the clock is off Asynchronously settableflip-flops 3220, 3230, and 3240 are set by the OR 3210 of TCXO_DIS andRESET. RESET_EFF is formed as the output of flip-flop 3240. The input offlip-flop 3240 is the output of flip-flop 3230, whose input is theoutput of flip-flop 3220. The input to flip-flop 3220 is set to zero.

In this example, SSBI_DATA should be very similar to SBDT, so that writeand read timing is relatively the same, regardless of whether or not theSSBI to SBI conversion occurs. Consider an example where SSBI_DATA issampled and SBDT is created with even one clock cycle delay. This wouldcause the slave SBI block (i.e. 1220) to see all accesses one cyclelater. For writes, this likely would not be a problem. For reads,though, when the returned data appears, it would come out one cyclelater than when the master device would be expecting it. As a result, itis necessary that the SSBI_DATA be fed onto SBDT without any registerdelays. As such, the next problem is to detect the start symbol andgenerate the SBST and SBCK signals in time to meet the SBI slave timing.This may be somewhat tricky, since in the duration of two symbols (thestart symbol and first data symbol), the SSBI slave converter 1420 needsto do the following: 1. Recognize the start symbol. 2. Force SBST toassert (go low). 3. Force SBCK low, then allow it to toggle such that afalling edge occurs every two clock cycles. 4. The second SBCK fallingedge will be used to sample SBDT in the SBI Slave.

Consider an example in which the SSBI_DATA line is in the idle state,then the SSBI slave converter 1420 samples the SSBI_DATA line onSSBI_CLK rising until it sees a start symbol. FIG. 33 illustrates thewaveforms for the start of the transfer. The start symbol is “found” andthe signal “deglitched” in half a clock cycle causing FOUND_ST toassert. This asynchronously forces SBST low, which in turn disables thecircuit searching for the start symbol. FOUND_ST is delayed half a clockcycle, ANDed with itself, then used to cause the first falling edge andrising edge of SBCK to occur. SBST and FOUND_ST are used together toenable SBCK to toggle. Since the SBI slave samples the symbols on SBCKfalling, they are effectively being sampled 25% into the symbol period.

Note that SSBI_CLK may not be lined up as shown. What is depicted inFIG. 33 is actually the “best” case. The “worst” case occurs such thatthe start symbol is not detected immediately, but rather a full clockcycle later. In this case, all the signals, FOUND_ST, SBST, SBCK shiftto the right by 1 clock cycle. Accordingly, the data symbols are beingsampled 75% into the symbol period. As will be apparent, for both cases,SBST and SBCK may be generated correctly with respect to SSBI_DATA. LATEis similar to the identically named signal, detailed above with respectto FIG. 25, which helps in reducing this one cycle of variability (inSBDT_PO and SBDT_OE) to half a clock cycle.

The waveforms for the end of a transfer are shown in FIG. 34. Capturingthe termination symbol may be somewhat complicated since it togglesevery clock cycle for four consecutive clock cycles. This exampletermination symbol is selected, because it is the shortest waveform thatis distinguishable from any symbol data. An example circuit used tosample this waveform basically samples SSBI_DATA over 4 clock cycleslooking for the pattern. A separate circuit operates in parallel butsampling on the falling clock edge. This is necessary since, if theSSBI_CLK rising edge is aligned with the termination symbol transitions,there's no guarantee the symbol will be caught by the first circuit.Hence, together, both circuits guarantee the termination symbol will befound.

FIG. 35 illustrates a portion of additional circuitry for an exampleSSBI slave converter 1420. The stretched reset, RESET_EFF, causesSBST_GEN and SBCK_GEN to asynchronously go high. The stretched reset isused to ensure it remains asserted until SSBI_CLK has turned on. Thisreset also resets part of the circuitry generating FOUND_T, detailedbelow.

SSBI_DATA is latched with SSBI_CLK in register 3508, which is reset withNOT SBST_GEN. The output of register 3508 is delivered as the input toregister 3510, clocked by the inverse of SSBI_CLK, also reset with NOTSBST_GEN. The output of register 3510 is labeled FOUND_ST, indicating astart has been found.

SSBI_DATA is also input to register 3502, clocked by the inverse ofSSBI_CLK. The output of register 3502 is input to register 3504, theoutput of which is labeled FOUND_ST_N. Both registers 3502 and 3504 arereset by RESET_EFF. FOUND_ST_N is latched in register 3506, clocked bySSBI_CLK, to produce LATE. Register 3506 is enabled by FOUND_ST.

FOUND_ST is used to asynchronously set flip-flop 3518, the output ofwhich is inverted 3520 to produce SBST_GEN. Thus, a found start bitasserts (drives low) SBST_GEN. Recall that NOT SBST_GEN resets theregisters 3508 and 3510 which generate FOUND_ST, thus FOUND_ST will bedeasserted until the current access or accesses are complete, and a newstart bit is found. Flip-flop 3518 is clocked by the inverse ofSSBI_CLK, and reset by RESET_EFF. A zero is clocked in when enabled byFOUND_T, which indicates a termination symbol has been found, detailedfurther below.

Register 3522, reset by RESET_EFF, takes FOUND_ST as an input and delaysit by a cycle. Its output, SBCK_EN, is delivered to NAND 3524, alongwith FOUND_ST, which is used to force SBCK_GEN low through AND 3526. Theother input to AND 3526 is used to generate SBCK_GEN when NAND 3524 isnot forcing SBCK_GEN low, and comes from the output of register 3514.Register 3514 is clocked by the inverse of SSBI_CLK, and isasynchronously set with RESET_EFF. Its output, in addition to beingdelivered to AND 3526, is inverted in inverter 3516. Its input isgenerated as the OR 3512 of SBST_GEN, FOUND_ST, FOUND_T, and the outputof inverter 3516. SBCK_EN and FOUND_T are used to stop SBCK fromtoggling before SBST de-asserts.

As described above, two circuits are deployed to identify thetermination symbol. In each circuit, SSBI_DATA is shifted into twoseries of 5 registers, 3528-3536 and 3542-3550, respectively. Thetermination symbol pattern is detected with two AND gates, 3538 and3552. The first circuit has register 3528 clocked by the inverse ofSSBI_CLK, and registers 3530-3536 clocked by SSBI_CLK. Registers 3528,3530, and 3532 are asynchronously reset by RESET_EFF. The terminationpattern is located with the AND 3538 of the inverse of register 3530,register 3532, the inverse of register 3534, and register 3536. Thesecond circuit has register 3542 clocked by SSBI_CLK, and registers3542-3550 clocked by the inverse of SSBI_CLK. Registers 3542, 3544, and3546 are asynchronously reset by RESET_EFF. The termination pattern islocated with the AND 3552 of the inverse of register 3544, register3546, the inverse of register 3548, and register 3550. The OR 3540 ofthe two circuits (whose outputs are the outputs of ANDs 3538 and 3552)creates FOUND_T, indicating a termination symbol has been found.

Note that FOUND_T may be 1 or 1.5 cycles long depending on whether oneor both circuits detect the termination symbol. This may constrain howquickly a subsequent transfer may be made on the bus. In the exampleembodiment, this will not cause any problem. In an alternate embodiment,a master can force SSBI_DATA to transfer an idle symbol for at least onesymbol period, if needed.

Note further that this circuit will not assert FOUND_T unless atermination-symbol is present. Given that data symbols change every twoclock cycles, if the clock is not aligned with the symbol transitions,sampling a symbol in two consecutive clock cycles will sample the samevalue, not the alternating value for the termination symbol. If thesampling clock is aligned with the symbol edges, then it may sampleeither the previous or new symbol value. As an example, consider a casewhere the first sample edge is aligned with the symbol transition, henceso is the third edge, but not the second and fourth, as those wouldoccur in the middle of a symbol. Keeping in mind that the desiredpattern is 1010, for the second and fourth samples to see a 0, the twodata symbols have to be 0. If that is true, then the third sample willhave to be 0, since the data did not change. As a result, FOUND_T willnot assert. A similar argument can be made for the case where the secondand fourth samples are aligned with symbol boundaries while the firstand third are not.

Again, note that SSBI_CLK may not be lined up as shown in FIGS. 33 and34. What is depicted is actually the “best” case. The “worst” caseoccurs such that the termination symbol is detected half a clock cyclelater. In this case, FOUND_T shifts to the right by half a clock cycle,which doesn't affect SBST or SBCK. As can be seen, for both “best” and“worst” cases, extra SBCK pulses are passed to the SBI Slave block. Itis expected that the SBI Slave will ignore the extra data bits once SBSTis deasserted.

LATE is used to alter the timing of the SBDT output when in SSBI_MODE.SBDT_OE_OUT is formed as the output of mux 3560, which takes as itsinputs SBDT_OE_IN and a delayed version, as latched in register 3558.Register 3558 takes SBDT_OE_IN as its input and delays the input by onecycle. SBDT_PO_OUT is formed as the output of mux 3566, which takes asits inputs SBDT_PO_IN and a delayed version, as latched in register3564. Register 3564 takes SBDT_PO_IN and delays the input by one cycle.The select for both muxes 3560 and 3566 is formed as the OR 3562 of LATEand NOT SSBI_MODE. Thus, when not in SSBI_MODE, SBDT_OE_OUT is selectedas SBDT_OE_IN, and SBDT_PO_OUT is selected as SBDT_PO_IN. The sameselection is made for both when in SSBI_MODE and LATE is not asserted.When LATE is asserted in SSBI_MODE, the delayed versions of SBDT_OE_INand SBDT_PO_IN are selected for their respective outputs.

RESET_TCXO_DIS is formed as the output of register 3556, which takes theoutput of register 3554 as its input. Register 3554 receives TXCO_DIS asits input. Register 3554 is clocked by SSBI_DATA. Register 3556 isclocked by the inverse of SSBI_DATA. Both registers are asynchronouslyreset by RESET. Thus, when TCXO_DIS is asserted, a rising edge ofSSBI_DATA sets register 3554, and a subsequent falling edge of SSBI_DATAsets register 3556, asserting RESET_TCXO_DIS. As such, SSBI_DATA can beused to assert RESET_TCXO_DIS, when the clock (i.e. SSBI_CLK, as well asother clocks) is disabled. In an example embodiment, RESET_TCXO_DIS maybe used to re-enable one or more disabled clocks.

Additional Alternate Embodiments

Additional embodiments are envisioned. For example, it may be desirableto interface newer SSBI slave devices with legacy SBI masters. As such,a 3-wire to 1-wire converter may be deployed, receiving the SBST, SBCK,and SBDT signals and generating a single SSBI_DATA signal therefrom.Such a converter may be deployed within an SSBI slave device, to allowfor either type of interface to be supported, without the use of an SBIslave, as detailed above. Alternately, such a converter may be added toa legacy master device, to intercept the 3-wire protocol and generate asingle wire interface therefrom. In other alternatives, the convertersdescribed herein may be deployed as standalone components, external toeither a master or slave of either type (SBI or SSBI).

Another embodiment of a slave may include both SBI and SSBI slaveinterfaces. A sensor may be deployed to monitor an incoming data line(which may be shared for both SSBI_DATA or SBDT), and determine whichtype of protocol is being used on the incoming lines. In thealternative, a slave may be programmable to select one slave interfaceor the other (SBI or SSBI). Those of skill in the art will recognizemyriad combinations of 3-wire and 1-wire masters, slaves, andconverters, which may be deployed within the scope of the presentinvention, in light of the teaching herein.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the embodiments disclosed herein may be implemented aselectronic hardware, computer software, or combinations of both. Toclearly illustrate this interchangeability of hardware and software,various illustrative components, blocks, modules, circuits, and stepshave been described above generally in terms of their functionality.Whether such functionality is implemented as hardware or softwaredepends upon the particular application and design constraints imposedon the overall system. Skilled artisans may implement the describedfunctionality in varying ways for each particular application, but suchimplementation decisions should not be interpreted as causing adeparture from the scope of the exemplary embodiments of the invention.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general purpose processor, a Digital SignalProcessor (DSP), an Application Specific Integrated Circuit (ASIC), aField Programmable Gate Array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with theembodiments disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in Random Access Memory (RAM), flashmemory, Read Only Memory (ROM), Electrically Programmable ROM (EPROM),Electrically Erasable Programmable ROM (EEPROM), registers, hard disk, aremovable disk, a CD-ROM, or any other form of storage medium known inthe art. An exemplary storage medium is coupled to the processor suchthat the processor can read information from, and write information to,the storage medium. In the alternative, the storage medium may beintegral to the processor. The processor and the storage medium mayreside in an ASIC. The ASIC may reside in a user terminal. In thealternative, the processor and the storage medium may reside as discretecomponents in a user terminal.

In one or more exemplary embodiments, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available media that can be accessed by acomputer. By way of example, and not limitation, such computer-readablemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that can be used to carry or store desired program code inthe form of instructions or data structures and that can be accessed bya computer. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition of medium.Disk and disc, as used herein, includes compact disc (CD), laser disc,optical disc, digital versatile disc (DVD), floppy disk and blu-ray discwhere disks usually reproduce data magnetically, while discs reproducedata optically with lasers. Combinations of the above should also beincluded within the scope of computer-readable media.

The previous description of the disclosed exemplary embodiments isprovided to enable any person skilled in the art to make or use thepresent invention. Various modifications to these exemplary embodimentswill be readily apparent to those skilled in the art, and the genericprinciples defined herein may be applied to other embodiments withoutdeparting from the spirit or scope of the invention. Thus, the presentinvention is not intended to be limited to the embodiments shown hereinbut is to be accorded the widest scope consistent with the principlesand novel features disclosed herein.

1. A master device configured to communicate with a slave device, andhaving a local clock that is isolated from and phase independent of alocal clock in the slave device, and further including circuitry forexchanging control and data with the slave device over a single wireserial bus at a clock rate determined by the local clock of the masterdevice.
 2. The master device of claim 1, wherein the single wire serialbus performs the exchanging of control and data in accordance with aSingle-Wire Serial Bus Interface protocol, which protocol does notinclude a clock line.
 3. The master device of claim 2, wherein thesingle wire serial bus performs the exchanging of control and data inaccordance with a Single-Wire Serial Bus Interface protocol, whichprotocol does not include a start/stop line.
 4. The master device ofclaim 3, wherein the circuitry includes logic for correcting any offsetsin phase and frequency between the clock rate of the master device andthe clock rate of the local clock in the slave device.
 5. The masterdevice of claim 1, wherein the single wire serial bus performs theexchanging of control and data in accordance with a Single-Wire SerialBus Interface protocol, which protocol does not include a start/stopline.
 6. The master device of claim 1, wherein the circuitry includeslogic for correcting any offsets in phase and frequency between theclock rate of the master device and the clock rate of the local clock inthe slave device.
 7. The master device of claim 1, wherein the singlewire serial bus performs the exchanging of control and data inaccordance with a Single-Wire Serial Bus Interface protocol, the masterdevice further comprising logic circuitry for converting the control anddata to the slave device into a three-wire interface signal, andoutputting same in a format compatible with the Serial Bus Interface(SBI) protocol.
 8. The master device of claim 1, wherein the masterdevice is configured to drive a plurality of slave devices over the samesingle-wire serial bus interface.
 9. The master device of claim 1,wherein the master device is configured to drive a plurality of slavedevices over plural single-wire serial bus interfaces associated witheach slave device.
 10. A slave device configured to communicate with amaster device, and having a local clock that is isolated from and phaseindependent of a local clock in the master device, and further includingcircuitry for exchanging control and data with the master device over asingle wire serial bus at a clock rate determined by the local clock ofthe slave device.
 11. The slave device of claim 10, wherein the singlewire serial bus performs the exchanging of control and data inaccordance with a Single-Wire Serial Bus Interface protocol, whichprotocol does not include a clock line.
 12. The slave device of claim11, wherein the single wire serial bus performs the exchanging ofcontrol and data in accordance with a Single-Wire Serial Bus Interfaceprotocol, which protocol does not include a start/stop line.
 13. Theslave device of claim 12, wherein the circuitry includes logic forcorrecting any offsets in phase and frequency between the clock rate ofthe slave device and the clock rate of the local clock in the masterdevice.
 14. The slave device of claim 10, wherein the single wire serialbus performs the exchanging of control and data in accordance with aSingle-Wire Serial Bus Interface protocol, which protocol does notinclude a start/stop line.
 15. The slave device of claim 10, wherein thecircuitry includes logic for correcting any offsets in phase andfrequency between the clock rate of the slave device and the clock rateof the local clock in the master device.
 16. The slave device of claim10, wherein the single wire serial bus performs the exchanging ofcontrol and data in accordance with a Single-Wire Serial Bus Interfaceprotocol, the slave device further comprising logic circuitry forconverting the control and data to the master device into a three-wireinterface signal, and outputting same in a format compatible with theSerial Bus Interface (SBI) protocol.
 17. The slave device of claim 10,wherein the slave device is configured in parallel with a plurality ofother slave devices all of which are configured to be coupled to thesame master device over the same single-wire serial bus interface. 18.The slave device of claim 10, wherein the slave device is configured inparallel with a plurality of other slave devices all of which areconfigured to be coupled to the same master device over dedicatedsingle-wire serial bus interface.
 19. A method of exchanging control anddata from a first device to a second device over a single wire serialbus interface, the method including clocking transmitted and receivedbits using a protocol that uses a local clock in the first device thatis isolated from and phase independent of a local clock in the seconddevice and at a clock rate determined by the local clock of the firstdevice.
 20. The method of claim 19, further comprising the first devicecorrecting any offsets in phase and frequency between the clock rate ofthe first device and the clock rate of the local clock in the seconddevice.
 21. A computer program product for use in a first deviceconfigured for exchanging control and data from a first device to asecond device over a single wire serial bus interface, the computerprogram product including instructions for causing the first device toclock transmitted and received bits using a protocol that uses a localclock in the first device that is isolated from and phase independent ofa local clock in the second device and at a clock rate determined by thelocal clock of the first device.
 22. The computer program product ofclaim 21, further comprising instructions for causing the first deviceto correct any offsets in phase and frequency between the clock rate ofthe first device and the clock rate of the local clock in the seconddevice.
 23. A device configured to communicate with a second device,including means for generating a local clock signal that is isolatedfrom and phase independent of a clock signal generated by the seconddevice, and further including means for exchanging control and data withthe second device over a single wire serial bus at a clock rate based onthe local clock signal of the device.
 24. The device of claim 23,wherein the single wire serial bus performs the exchanging of controland data in accordance with a Single-Wire Serial Bus Interface protocol,which protocol does not include a clock line.
 25. The device of claim24, wherein the single wire serial bus performs the exchanging ofcontrol and data in accordance with a Single-Wire Serial Bus Interfaceprotocol, which protocol does not include a start/stop line.
 26. Thedevice of claim 25, wherein the means for exchanging includes means forcorrecting any offsets in phase and frequency between the clock rate ofthe device and the clock rate of the local clock signal in the seconddevice.
 27. The device of claim 23, wherein the single wire serial busperforms the exchanging of control and data in accordance with aSingle-Wire Serial Bus Interface protocol, which protocol does notinclude a start/stop line.
 28. The device of claim 23, wherein the meansfor exchanging includes means for correcting any offsets in phase andfrequency between the clock rate of the device and the clock rate of thelocal clock signal in the second device.